From mboxrd@z Thu Jan 1 00:00:00 1970 To: 9fans@cse.psu.edu From: ozan s yigit Message-ID: References: <3C914E64.D5D00447@null.net>, <4da3d9af.0203150929.1d3154d2@posting.google.com>, <87r8mlhez8.fsf@becket.becket.net> Subject: Re: macro fun [Re: [9fans] plan or side effect] Date: Thu, 21 Mar 2002 11:01:30 +0000 Topicbox-Message-UUID: 6b8628f4-eaca-11e9-9e20-41e7f4b1d025 "Thomas Bushnell, BSG" 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 or . (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