Path: utzoo!attcan!utgpu!jarvis.csri.toronto.edu!mailrus!ncar!gatech!galbp!advdev.LBP.HARRIS.COM!jsb
From: jsb@advdev.LBP.HARRIS.COM (FLEA)
Newsgroups: comp.lang.c
Subject: Re: want to know
Message-ID: <8496@galbp.LBP.HARRIS.COM>
Date: 18 Aug 89 13:13:44 GMT
References: <8487@bsu-cs.bsu.edu> <2980@solo9.cs.vu.nl> <182@sunquest.UUCP> <14269@haddock.ima.isc.com> <1496@l.cc.purdue.edu> <1701@crdgw1.crd.ge.com> <2538@trantor.harris-atd.com> <1989Aug16.203219.11825@cs.rochester.edu> <2549@trantor.harris-atd.com> <10770@smoke.
Sender: news@galbp.LBP.HARRIS.COM
Reply-To: jsb@advdev.UUCP (FLEA)
Lines: 12

# In article <10770@smoke.BRL.MIL> gwyn@brl.arpa (Doug Gwyn) writes:
# >Speak for yourself.  The C compiler I use at home processes the main()
# >pseudo-function differently from other functions, and in general any
# >Standard-conforming implementation is going to have to give some degree
# >of special treatment to main(), since it doesn't follow quite the same
# >rules as normal C functions.

I'm curious.  What does your C compiler at home do differently with main()
and why is it a "pseudo-function"?
What different rules does it follow?

Jeff "Out-of-touch-with-standards-but-it-didn't-use-to-be-that-way" Barber