PE>>> You can pick up most of my programs and compile them any damn
PE>>> place you want.  C has a very well-defined standard, which is
PE>>> very very good.  Anything you can depend upon is documented.
BV>> Hmmm...Strange...MSC v5.1 and Visual C++ 1.5 both barf on PKTJOIN

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.

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

I forget why MSC 8.0 spits the dummy and can't be bothered looking
right at this moment. Relax Paul, I was really only rattling your
cage, although even your stuff isn't as "pure" as you might like.

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?

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

Cheers, Brenton
@EOT:

---