From: ozan s yigit <oz@blue.cs.yorku.ca>
To: 9fans@cse.psu.edu
Subject: Re: macro fun [Re: [9fans] plan or side effect]
Date: Thu, 21 Mar 2002 11:01:30 +0000 [thread overview]
Message-ID: <vi4y9gndsny.fsf@blue.cs.yorku.ca> (raw)
In-Reply-To: <87r8mlhez8.fsf@becket.becket.net>
"Thomas Bushnell, BSG" <tb+usenet@becket.net> writes:
> Some users try to use `-pedantic' to check programs for strict ANSI C
> conformance. They soon find that it does not do quite what they
> want: it finds some non-ANSI practices, but not all--only those for
> which ANSI C *requires* a diagnostic.
thanks. old habits die hard. i'll read the current documentation and
the standard carefully before my next abuse of the compiler, which will
be a monthly event. :)
> A feature to report any failur to conform to ANSI C might be useful
> in some instances, but would require considerable additional work and
> would be quite different from `-pedantic'.
indeed, and i don't know if gcc should necessarily try to do this sort
of analysis. unfortunately no lint i have access to (including the quite
superior sun lint) would complain. lclint sort of does, but it doesn't
get it right:
boyd.c:3:14: Name strcpy is reserved for future ANSI library extensions.
Functions that begin with "str" and a lowercase letter may be added to
<stdlib.h> or <string.h>. (See ANSI, Section 4.13.7)
External name is reserved for system in ANSI standard. (-ansireserved will
suppress message)
i did not try any harder.
oz
--
The more I live with #ifdef, the less I like it. -- henry spencer
next prev parent reply other threads:[~2002-03-21 11:01 UTC|newest]
Thread overview: 39+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-02-28 17:41 [9fans] plan or side effect David Gordon Hogan
2002-03-01 10:02 ` Thomas Bushnell, BSG
2002-03-01 12:07 ` Boyd Roberts
2002-03-04 10:04 ` Thomas Bushnell, BSG
2002-03-04 17:11 ` Sean Quinlan
2002-03-04 18:23 ` ozan s yigit
2002-03-05 9:41 ` Thomas Bushnell, BSG
2002-03-05 9:56 ` Boyd Roberts
2002-03-05 9:43 ` Boyd Roberts
2002-03-08 17:30 ` Thomas Bushnell, BSG
2002-03-08 18:00 ` Dan Cross
2002-03-11 10:04 ` Ralph Corderoy
2002-03-11 10:04 ` Thomas Bushnell, BSG
2002-03-14 9:56 ` macro fun [Re: [9fans] plan or side effect] ozan s. yigit
2002-03-15 10:18 ` Thomas Bushnell, BSG
2002-03-15 10:18 ` Douglas A. Gwyn
2002-03-15 17:48 ` ozan s. yigit
2002-03-15 18:40 ` Mike Haertel
2002-03-18 10:38 ` ozan s yigit
2002-03-15 18:42 ` Mike Haertel
2002-03-18 10:32 ` Thomas Bushnell, BSG
2002-03-18 10:33 ` Thomas Bushnell, BSG
2002-03-21 11:01 ` ozan s yigit [this message]
2002-03-18 10:33 ` Ralph Corderoy
2002-03-19 9:49 ` Douglas A. Gwyn
2002-03-21 11:01 ` Ralph Corderoy
2002-03-18 10:38 ` AMSRL-CI-CN
2002-03-20 13:38 ` Boyd Roberts
2002-03-18 10:38 ` ozan s. yigit
2002-03-18 13:08 ` Wladimir Mutel
2002-03-19 9:49 ` ozan s. yigit
2002-03-19 9:49 ` Douglas A. Gwyn
2002-03-19 16:01 ` ozan s yigit
2002-03-01 11:57 ` [9fans] plan or side effect Boyd Roberts
2002-03-18 11:22 macro fun [Re: [9fans] plan or side effect] forsyth
2002-03-18 17:37 ` Thomas Bushnell, BSG
2002-03-18 18:05 forsyth
2002-03-19 9:50 ` Douglas A. Gwyn
2002-03-19 10:57 forsyth
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=vi4y9gndsny.fsf@blue.cs.yorku.ca \
--to=oz@blue.cs.yorku.ca \
--cc=9fans@cse.psu.edu \
/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 NNTP newsgroup(s).