Path: utzoo!utgpu!jarvis.csri.toronto.edu!mailrus!tut.cis.ohio-state.edu!erd From: erd@tut.cis.ohio-state.edu (Ethan R. Dicks) Newsgroups: comp.sys.amiga.tech Subject: Re: Lattice startup code questions Keywords: C Startup small how? Message-ID: <36926@tut.cis.ohio-state.edu> Date: 24 Feb 89 16:09:23 GMT References: <9322@bloom-beacon.MIT.EDU> <90452@sun.uucp> <6054@cbmvax.UUCP> <90987@sun.uucp> Reply-To: Ethan R. Dicks Organization: Ohio State University Computer and Information Science Lines: 26 In article <90987@sun.uucp> cmcmanis@sun.UUCP (Chuck McManis) writes: >In article <6054@cbmvax.UUCP> jesup@cbmvax.UUCP (Randell Jesup) writes: >> Please, use exit() or equivalent (XCEXIT in lattice c.a) instead >>of Exit(). Exit is really more for BCPL, and with most compilers you >>should call a cleanup routine. Look at c.a, once again. > >Randell missed the point, maybe you did too. *Don't* use the compiler >exit() if you *didn't* use the compiler startup file. OK... so to those who know... what should we do? I have been writing code for Lattice (currently 5.0, soon to be 5.02) without linking in the startup module. I looked back at my code and noticed that I never call any exit() type of function; I just close all my braces and let main() end. Should I be calling an exit()? Is there a list of hints and tips for those people, like myself, who write C without linking in startup code? Thanks, -ethan -- Ethan R. Dicks | ###### This signifies that the poster is a member in Software Results Corp| ## good sitting of Inertia House: Bodies at rest. 940 Freeway Drive N. | ## Columbus OH 43229 | ###### "You get it, you're closer.