From: Zack Weinberg <zack@codesourcery.com>
To: Neil Booth <neil@daikokuya.co.uk>
Cc: Gabriel Dos Reis <gdr@integrable-solutions.net>, gcc@gcc.gnu.org
Subject: Re: Warning for trigraphs in comment?
Date: Sun, 18 May 2003 20:14:00 -0000 [thread overview]
Message-ID: <874r3sdo23.fsf@egil.codesourcery.com> (raw)
In-Reply-To: <20030518193209.GD13596@daikokuya.co.uk> (Neil Booth's message of "Sun, 18 May 2003 20:32:09 +0100")
Neil Booth <neil@daikokuya.co.uk> writes:
> Zack Weinberg wrote:-
>
>> > is extracted from Herb's GTW #86 -- full message appended below.
>> > I would suggest we warn for trigraphs in comments.
>>
>> This was discussed a couple weeks back. 3.4 now warns about ??/\n in
>> a comment. The change is self-contained and could be put into 3.3.1
>> if people think that's a good idea.
>
> It's part of the complete reorganization of line lexing, so I don't
> think it's an easy patch for 3.3. I'd be happy to be proved wrong
> though.
My bad, I was thinking only about the patch itself, not its
dependencies.
I don't have time to try to reimplement it over 3.3.1's codebase, but
if someone else wants to take a stab at it I don't think it'd be all
that bad.
zw
next prev parent reply other threads:[~2003-05-18 20:03 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-05-18 13:37 Gabriel Dos Reis
2003-05-18 18:54 ` Zack Weinberg
2003-05-18 20:01 ` Neil Booth
2003-05-18 20:14 ` Zack Weinberg [this message]
2003-05-19 6:57 ` Gabriel Dos Reis
2003-05-18 19:36 ` Neil Booth
2003-05-19 6:51 ` Gabriel Dos Reis
2003-05-19 13:22 ` Paul Koning
2003-05-19 14:35 ` Zack Weinberg
2003-05-19 14:37 ` Paul Koning
2003-05-19 14:51 ` Gabriel Dos Reis
2003-05-19 14:55 ` Paul Koning
2003-05-19 18:11 ` Joe Buck
2003-05-19 20:04 ` Neil Booth
2003-05-19 15:10 ` Zack Weinberg
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=874r3sdo23.fsf@egil.codesourcery.com \
--to=zack@codesourcery.com \
--cc=gcc@gcc.gnu.org \
--cc=gdr@integrable-solutions.net \
--cc=neil@daikokuya.co.uk \
/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).