From: Zack Weinberg <zack@codesourcery.com>
To: "Dave Korn" <dk@artimi.com>
Cc: "'Adam Monsen'" <haircut@gmail.com>, <gcc@gcc.gnu.org>
Subject: Re: warn/croak on "string" "string" auto-joins
Date: Tue, 17 Aug 2004 18:55:00 -0000 [thread overview]
Message-ID: <87r7q539o9.fsf@codesourcery.com> (raw)
In-Reply-To: <NUTMEGTosnwO5UGXtTG00000dd2@NUTMEG.CAM.ARTIMI.COM> (Dave Korn's message of "Tue, 17 Aug 2004 19:07:37 +0100")
"Dave Korn" <dk@artimi.com> writes:
>> -----Original Message-----
>> From: Zack Weinberg
>> Sent: 17 August 2004 19:01
>
>> "Dave Korn" writes:
>>
>> > 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"?
>>
>> I'm wondering how useful it would be without lint-markup even if it
>> *did* default to off.
>>
>> zw
>
>
> Point taken. Maybe a more useful set of options than "on/off" would be
> "on/off/off in system headers but on in application files"
All warnings are off in system headers anyway.
Why don't you and Adam talk this over and come up with a specification
that would work for you?
zw
next prev parent reply other threads:[~2004-08-17 18:24 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
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 [this message]
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=87r7q539o9.fsf@codesourcery.com \
--to=zack@codesourcery.com \
--cc=dk@artimi.com \
--cc=gcc@gcc.gnu.org \
--cc=haircut@gmail.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).