home *** CD-ROM | disk | FTP | other *** search
- Path: sparky!uunet!spool.mu.edu!yale.edu!ira.uka.de!chx400!sicsun!disuns2!disuns2.epfl.ch!simon
- From: simon@lia.di.epfl.ch (Simon Leinen)
- Newsgroups: comp.sys.sgi
- Subject: Re: Bug in SGI ansi compliance (or are the others wrong ?)
- Message-ID: <SIMON.92Nov12111146@liasg2.epfl.ch>
- Date: 12 Nov 92 10:11:46 GMT
- References: <s5c02sg@sgi.sgi.com> <1992Nov11.225422.2888@bernina.ethz.ch>
- Sender: news@disuns2.epfl.ch
- Organization: DI-LIA -- Ecole Polytechnique Federale de Lausanne
- Lines: 15
- Nntp-Posting-Host: liasg2.epfl.ch
- In-reply-to: hoesel@igc.ethz.ch's message of 11 Nov 92 22:54:22 GMT
- X-Md4-Signature: 4931a1eb0301df8b48bf3a2d9b6facf1
-
- In article <1992Nov11.225422.2888@bernina.ethz.ch> hoesel@igc.ethz.ch
- (Frans van Hoesel) writes:
-
- You might find it a '(normally minor)annoyance' but lex produces
- code that does *NOT* compile using -ansi, exactly because of the
- above reason!! (you can check that easely by creating a file with
- two lines of '%%' (a minimal lex program) run lex with it, and try
- to compile with -ansi)
-
- I don't think anyone claims that LEX generates ANSI C, so you
- shouldn't use -ansi anyway. I'm not sure whether the offending LEX
- output (an initialization of a static variable to "stdout" or
- something like that) is allowed by the standard.
- --
- Simon.
-