PE>>> MSC 5.1 is not a conforming implementation.
 BV>> True, but what about Visual C++ 1.5 ne: MSC 8.0 ?

 PE>> I don't know about Visual C++, but if MSC 8.0 doesn't have
 PE>> EXIT_SUCCESS in the  header (or something included
 PE>> by it), I would be willing to say 3 times in the AUST_C_HERE
 PE>> echo "I am a Borland Fan" (to the tune of "The Itchy and
 PE>> Scratchy Show" title as shown on the Simpsons).  Can you do
 PE>> a search for these definitions in  to see if they
 PE>> have been #ifdef'd out unless you do something-or-other.

 BV> Nah, you're safe there :)
 BV> I failed to mention that they both barf on it for different reasons :)

 BV> I forget why MSC 8.0 spits the dummy and can't be bothered looking
 
I am *very* interested to know why it would complain about
EXIT_SUCCESS, so I would appreciate it if you would take the
time to revisit that problem. 
 
 BV> right at this moment. Relax Paul, I was really only rattling your
 BV> cage, although even your stuff isn't as "pure" as you might like.
 
It *is* pure.  It will compile on any ISO conforming C compiler.

 PE>> Well you should be - about MSC 5.1.  Get a REAL compiler!
 BV>> ROFL...that fits on one 360k floppy ? Are you for real ? :)
 PE>> What about a 1.4 meg/1.2 meg floppy?  How often do you have to
 PE>> do your development on a machine without one of those?

 BV> I don't. My point was that it doesn't take any space at all, compared
 BV> to the 60+ Mb monsters which they all ship now. For this reason I leave
 BV> it on my system and if I am doing a quick and dirty command line thing
 BV> then I will more often than not use it as it is more than acceptable.

I do quick and dirty command line things too, but I do them 
with 60+ Mb monsters.  I don't see that it causes me any
great stress.  The stress only comes when I have this
insatiable desire to keep 10 60+ Mb monsters on my machine
all at the same time!  BFN.  Paul.
@EOT:

--- Mksmsg