From: Joern Rennecke <amylaar@cygnus.co.uk>
To: eggert@twinsun.com (Paul Eggert)
Cc: gavin@cygnus.com, phdm@macqel.be, gcc2@cygnus.com, egcs@cygnus.com
Subject: Re: #elsif
Date: Thu, 09 Apr 1998 17:44:00 -0000 [thread overview]
Message-ID: <199804091749.SAA03727@phal.cygnus.co.uk> (raw)
In-Reply-To: <199804082200.PAA28005@shade.twinsun.com>
> I assume that you do not want to make a special case for `elsif' only.
> (That would be odd; it wouldn't catch other misspellings like `elseif'.)
Yes, if we warn for elsif, we should have a like warning for elseif.
Both are misspellings of elif that mirror a programming language and
might thus be mistaken for the real thing. They are special because they
are supposedly meant to end the commenting out. If there were likely
misspellings of #endif that could be mistaken for the real thing doe to
the similarity with another language (hmmm... maybe #fi would qualify?),
that these should also be warned about.
The warning for such a specific test should not just be something
vanilla like unrecognized #-directive, since that could make people
think we warned about all unrecognized directives.
It should somehow point out the assumed error.
next prev parent reply other threads:[~1998-04-09 17:44 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
1998-04-07 6:54 #elsif Philippe De Muyter
1998-04-07 19:34 ` #elsif Paul Eggert
1998-04-08 9:27 ` #elsif Joern Rennecke
1998-04-08 15:08 ` #elsif Gavin Romig-Koch
1998-04-08 23:35 ` #elsif Paul Eggert
1998-04-08 21:20 ` #elsif Philippe De Muyter
1998-04-08 21:13 ` #elsif Paul Eggert
1998-04-09 8:27 ` #elsif Joe Buck
1998-04-09 3:09 ` #elsif Nick Ing-Simmons
1998-04-08 21:45 ` #elsif Gavin Romig-Koch
1998-04-09 17:44 ` Joern Rennecke [this message]
[not found] ` <199804080118.SAA26855.cygnus.egcs@shade.twinsun.com>
1998-04-08 15:08 ` #elsif Ulrich Drepper
1998-04-08 2:13 #elsif SXTHREE
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=199804091749.SAA03727@phal.cygnus.co.uk \
--to=amylaar@cygnus.co.uk \
--cc=egcs@cygnus.com \
--cc=eggert@twinsun.com \
--cc=gavin@cygnus.com \
--cc=gcc2@cygnus.com \
--cc=phdm@macqel.be \
/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).