Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Path: utzoo!mnetor!seismo!columbia!rutgers!dayton!viper!john
From: john@viper.UUCP (John Stanley)
Newsgroups: comp.lang.c
Subject: Re: Use of #pragma
Message-ID: <890@viper.UUCP>
Date: Fri, 24-Apr-87 16:44:44 EST
Article-I.D.: viper.890
Posted: Fri Apr 24 16:44:44 1987
Date-Received: Sun, 26-Apr-87 01:12:45 EST
References: <IUXhaCy00V4FwZ00ZD@andrew.cmu.edu>
Reply-To: john@viper.UUCP (John Stanley)
Organization: DynaSoft Systems
Lines: 22

In article <IUXhaCy00V4FwZ00ZD@andrew.cmu.edu> 
jm36#@andrew.cmu.edu (John Gardiner Myers) writes:
 >
 >I certainly hope you don't try to feed a file like that through the
 >GNU C compiler anytime between 9AM and 5PM on weekdays.
 >
 >From the documentation on the GNU preprocessor:
 >> 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.

  (wiping tears from eyes :^)

  Thanks for that tidbit John, I haven't laughed that hard in -months-!

--- 
John Stanley (john@viper.UUCP)
Software Consultant - DynaSoft Systems
UUCP: ...{amdahl,ihnp4,rutgers}!{meccts,dayton}!viper!john