From: Horst von Brand <vonbrand@inf.utfsm.cl>
To: Gareth Hughes <gareth.hughes@acm.org>
Cc: paulr <reichp@ameritech.net>, linux-kernel@vger.kernel.org
Subject: Re: 2.4.7 -- GCC-3.0 -- "multiline string literals deprecated" -- PATCH
Date: Tue, 31 Jul 2001 10:15:09 -0400 [thread overview]
Message-ID: <200107311415.f6VEF9oD028247@pincoya.inf.utfsm.cl> (raw)
In-Reply-To: Message from Gareth Hughes <gareth.hughes@acm.org> of "Tue, 31 Jul 2001 23:52:56 +1000." <3B66B838.C8B427B1@acm.org>
Gareth Hughes <gareth.hughes@acm.org> said:
[...]
> Yes, unfortunately GCC 3.0 deprecated multiline string literals
AFAIU, they are non-standard, and can easily hide bugs (in opening a string
and forgetting to close you are in escence commenting out lines of code)
> -- I saw
> someone arguing on the GCC mailing lists that writing large chunks of
> inline asm shouldn't be "easy",
Right. If you use a compiler, you shouldn't need it much. Better make
other, more important, things easy/more foolproof, even at some cost for
the asm() writer. (Hint: Count the lines of asm in the kernel (an
_extremely_ heavy asm user!) vs the lines of plain C)
> as it interferes with the compiler's
> optimization passes. There were other such braindead arguments
> supporting the deprecation.
Yep, this is a braindead argument. There must have been others (sensible
ones)...
> The thread should be pretty easy to find in
> the archives. Don't know if the deprecation will be removed in future
> versions.
I hope they disallow multiline strings pretty soon.
--
Dr. Horst H. von Brand Usuario #22616 counter.li.org
Departamento de Informatica Fono: +56 32 654431
Universidad Tecnica Federico Santa Maria +56 32 654239
Casilla 110-V, Valparaiso, Chile Fax: +56 32 797513
next prev parent reply other threads:[~2001-07-31 14:15 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-07-31 4:57 paulr
2001-07-31 13:52 ` Gareth Hughes
2001-07-31 14:11 ` Matti Aarnio
2001-07-31 14:15 ` Horst von Brand [this message]
2001-07-31 15:57 ` Gareth Hughes
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=200107311415.f6VEF9oD028247@pincoya.inf.utfsm.cl \
--to=vonbrand@inf.utfsm.cl \
--cc=gareth.hughes@acm.org \
--cc=linux-kernel@vger.kernel.org \
--cc=reichp@ameritech.net \
/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
all inboxes | Powered by JetHome®