From mboxrd@z Thu Jan  1 00:00:00 1970
From: Christopher Faylor <cgf@redhat.com>
To: gdb@sources.redhat.com
Subject: Re: GCC is depreciating multi-line strings
Date: Wed, 21 Mar 2001 15:59:00 -0000
Message-id: <20010320182104.B1433@redhat.com>
References: <200103202016.MAA27812@bosch.cygnus.com> <1010320205618.ZM10795@ocotillo.lan> <3AB7C47F.58BEB30B@redhat.com> <3AB7DEDF.29B4CB8E@home.com> <3AB7E20F.E9DCDE23@cygnus.com>
X-SW-Source: 2001-03/msg00208.html

On Tue, Mar 20, 2001 at 06:04:47PM -0500, Andrew Cagney wrote:
>Um, I'm slightly confused.  What exactly is ment by multi-line strings? 
>I've found this link and am still looking :-)
>
> http://gcc.gnu.org/ml/gcc/2001-03/msg00855.html

Cygwin has been bit by this recent change.

a = "This is
the multiline string
that has been deprecated.";

gcc stores that as three separate lines.

The "correct" way to do this is:

a = "This is\n\
the multiline string\n\
which has not been deprecated.";

This is also ok, of course:

a = "abc\
def";

It is equivalent to:

a = "abcdef";

The reason for deprecating the non \ usage is that it is not portable.

If gdb uses this construct, I have a hard time believing that this could
be true.

A quick grep seems to show that gdb is doing the right thing so I really
don't think that this is an issue.

cgf