Path: utzoo!utgpu!jarvis.csri.toronto.edu!clyde.concordia.ca!uunet!portal!cup.portal.com!thad
From: thad@cup.portal.com (Thad P Floryan)
Newsgroups: comp.sys.amiga
Subject: Re: #pragma PREPROCESSOR control is evil!
Message-ID: <25595@cup.portal.com>
Date: 4 Jan 90 13:57:52 GMT
References: <10415@etana.tut.fi> <9532@microsoft.UUCP>
  <411@enuxha.eas.asu.edu> <6@microsoft.UUCP> <25206@cup.portal.com>
  <10033@microsoft.UUCP> <1410@sas.UUCP>
Organization: The Portal System (TM)
Lines: 19

Doug Walker brings up some GOOD questions about "#pragma".  For all the
good it (#pragma) does, it may as well be renamed "#fragme" or "#smegma".

(If you don't know the genesis of "frag" (Viet Nam war era), don't ask.)

The ANSI-conforming definition of #pragma in the GNU ``C'' compiler is the
best one I've ever seen; from the GNU docs:

"	The `#pragma' command is specified in the ANSI standard to have an
	arbitrary implementation-defined effect.  In the GNU C preprocessor,
	`#pragma' first attempts to run the game `rogue'; if that fails,
	it tries to run the game `hack'; if that fails, it tries to run
	GNU Emacs displaying the Tower of Hanoi; if that fails, it reports a
	fatal error.  In any case, preprocessing does not continue.
"

Enjoy!

Thad Floryan [ thad@cup.portal.com (OR) ..!sun!portal!cup.portal.com!thad ]