Mirror of the gdb mailing list
 help / color / mirror / Atom feed
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	[thread overview]
Message-ID: <20010320182104.B1433@redhat.com> (raw)
In-Reply-To: <3AB7E20F.E9DCDE23@cygnus.com>

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


  reply	other threads:[~2001-03-21 15:59 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-03-21 15:59 Merging manuals (was Re: How do you use GDB to debug GDB) Michael Elizabeth Chastain
2001-03-21 15:59 ` Andrew Cagney
2001-03-21 15:59 ` Kevin Buettner
2001-03-21 15:59   ` Fernando Nasser
2001-03-21 15:59     ` GCC is depreciating multi-line strings Stephen Smith
2001-03-21 15:59       ` Andrew Cagney
2001-03-21 15:59         ` Christopher Faylor [this message]
2001-03-21 15:59         ` Andrew Cagney
2001-03-21 15:59 ` Merging manuals (was Re: How do you use GDB to debug GDB) Eli Zaretskii
2001-03-21 15:59   ` J.T. Conklin

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20010320182104.B1433@redhat.com \
    --to=cgf@redhat.com \
    --cc=gdb@sources.redhat.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox