home *** CD-ROM | disk | FTP | other *** search
- Newsgroups: comp.lang.c
- Path: sparky!uunet!spillman!tye
- From: tye@spillman.uucp (E. Tye McQueen)
- Subject: Re: Another C palindrome puzzle
- Message-ID: <1992Dec29.092627.26362@spillman.uucp>
- Date: Tue, 29 Dec 1992 09:26:27 GMT
- References: <9234503.17437@mulga.cs.mu.OZ.AU> <9235703.672@mulga.cs.mu.OZ.AU> <1992Dec23.172745.12170@thunder.mcrcim.mcgill.edu> <9236108.5556@mulga.cs.mu.OZ.AU>
- Organization: Spillman Data Systems
- Lines: 26
-
- fjh@munta.cs.mu.OZ.AU (Fergus James HENDERSON) writes:
- )mouse@thunder.mcrcim.mcgill.edu (der Mouse) writes:
- )>Or older versions of gcc, which would give up on compiling and
- )>run rogue when they happened across a #pragma of any sort?
- )
- )I think that these versions of gcc are not standard-conforming.
- )I don't have the ANSI C standard, but the C++ ARM says that
- )"an unrecognized pragma will be ignored", and I think that the
- )C standard says something similar.
-
- But, of course, that gcc compiler recognized all pragmas.
-
- )But you're right of course, it's not strictly ANSI conforming.
-
- You seem to be saying that any use of "#pragma" results in a
- not-strictly-ANSI-conforming program, which makes it seem silly
- to include it as part of the standard. And illustrating that
- point was, as I recall, the main reason that gcc chose to run
- rogue. Though I at least partially agree, I doubt that is, in
- fact, what you are were saying; so I apologize for misunder-
- standing you.
-
- tye@spillman.com Tye McQueen, E.
- ----------------------------------------------------------
- Nothing is obvious unless you are overlooking something.
- ----------------------------------------------------------
-