From bug-request at octave dot org Tue Dec 21 11:46:47 2004
Subject: multiline string fix
From: "John W. Eaton" <jwe at bevo dot che dot wisc dot edu>
To: =?UTF-8?B?TWljaGFsIMSMaWhhxZk=?= <mcihar at suse dot cz>
Cc: bug at octave dot org
Date: Tue, 21 Dec 2004 12:48:01 -0500

On 21-Dec-2004, Michal $,1 ,(Biha$,1 y(B <mcihar at suse dot cz> wrote:

| recent gcc versions reject multi line string constats, attached patch
| fixes octave compilation with them.

Which version of GCC rejects this code?  What is the precise error
message?

There are many many more parts of Octave where string constants are
written in the style

  "foo\n\
bar"

which as far as I am aware is not a multi-line string constant, but a
string constant written with an escaped newline (which then
disappears).  Is that not correct?

In any case, if we really can't write strings with escaped newlines,
then I would expect many more files with problems in addition to
fsolve.cc.  Perhaps there is some other explanation for the error you
saw?  Does fsolve.cc have a line where the backslash at the end of the
line is followed by something other than a newline character?

jwe



-------------------------------------------------------------
Octave is freely available under the terms of the GNU GPL.

Octave's home on the web:  http://www.octave.org
How to fund new projects:  http://www.octave.org/funding.html
Subscription information:  http://www.octave.org/archive.html
-------------------------------------------------------------