public inbox for gcc@gcc.gnu.org
 help / color / mirror / Atom feed
From: "Dave Korn" <dk@artimi.com>
To: "'Zack Weinberg'" <zack@codesourcery.com>,
	"'Adam Monsen'" <haircut@gmail.com>
Cc: <gcc@gcc.gnu.org>
Subject: RE: warn/croak on "string" "string" auto-joins
Date: Tue, 17 Aug 2004 18:02:00 -0000	[thread overview]
Message-ID: <NUTMEGR3TOkIt1tF0Lu00000dd0@NUTMEG.CAM.ARTIMI.COM> (raw)
In-Reply-To: <874qn14pvc.fsf@codesourcery.com>


> -----Original Message-----
> From: gcc-owner On Behalf Of Zack Weinberg
> Sent: 17 August 2004 18:49

> Adam Monsen writes:
> 
> > String auto-joins can be dangerous. Is there a way to tell the
> > compiler to warn/croak when an auto-join occurs?
> 
> There is not, and without a way for the programmer to make clear that
> a given use of string-constant concatenation is intentional, I am
> reluctant to add one.
> 
> zw

  Yeh.  What if you really *did* want to talk about your "Crayon-line
drawing routines"?

  More seriously though, I don't see why there shouldn't be one, but rather
than make coders go through and lint-markup every place where we really
meant to concat two strings in a macro (one of which has only just been
en-quoted), maybe the warning should just default to "off"?

    cheers, 
      DaveK
-- 
Can't think of a witty .sigline today....

  reply	other threads:[~2004-08-17 17:52 UTC|newest]

Thread overview: 34+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-08-17 17:37 Adam Monsen
2004-08-17 17:52 ` Zack Weinberg
2004-08-17 18:02   ` Dave Korn [this message]
2004-08-17 18:09     ` Zack Weinberg
2004-08-17 18:12       ` Dave Korn
2004-08-17 18:20         ` Andrew Pinski
2004-08-17 18:55         ` Zack Weinberg
2004-08-17 18:24       ` Adam Monsen
2004-08-17 23:25     ` Robert Dewar
2004-08-17 23:20   ` Robert Dewar
2004-08-17 23:25     ` Stan Shebs
2004-08-18  0:21       ` Robert Dewar
2004-08-18  2:43     ` Mike Stump
2004-08-18 13:16     ` Paul Koning
2004-08-18 18:08       ` Dave Korn
2004-08-19 21:20     ` Kai Henningsen
2004-08-19 21:31       ` Chris Jefferson
2004-08-20 16:25         ` Kai Henningsen
2004-08-19 21:32       ` Michael N. Moran
2004-08-19 21:53       ` Janis Johnson
2004-08-19 23:23       ` Florian Weimer
2004-08-20 16:49         ` Kai Henningsen
2004-08-17 23:02 ` Robert Dewar
2004-08-17 23:26 Gabor Greif
2004-08-18  0:22 ` Adam Monsen
2004-08-18  0:49   ` Gabor Greif
2004-08-18 10:15     ` Dave Korn
2004-08-18 10:55       ` Chris Jefferson
2004-08-18 11:17         ` Mathieu Lacage
2004-08-18 11:19           ` Chris Jefferson
2004-08-18 11:36             ` Mathieu Lacage
2004-08-18 14:07               ` Robert Dewar
2004-08-18 12:55         ` Andreas Schwab
2004-08-20 11:27         ` Per Abrahamsen

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=NUTMEGR3TOkIt1tF0Lu00000dd0@NUTMEG.CAM.ARTIMI.COM \
    --to=dk@artimi.com \
    --cc=gcc@gcc.gnu.org \
    --cc=haircut@gmail.com \
    --cc=zack@codesourcery.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).