Path: utzoo!utgpu!news-server.csri.toronto.edu!bonnie.concordia.ca!thunder.mcrcim.mcgill.edu!snorkelwacker.mit.edu!usc!elroy.jpl.nasa.gov!ncar!hsdndev!cmcl2!adm!smoke!gwyn
From: gwyn@smoke.brl.mil (Doug Gwyn)
Newsgroups: comp.lang.c
Subject: Re: An Ubiquitous C bug
Message-ID: <14940@smoke.brl.mil>
Date: 23 Jan 91 22:48:41 GMT
References: <s64421.664471332@zeus> <1991Jan21.164725.10287@demott.com> <s64421.664559119@zeus>
Organization: U.S. Army Ballistic Research Laboratory, APG, MD.
Lines: 9

In article <s64421.664559119@zeus> s64421@zeus.usq.EDU.AU (house ron) writes:
>I tried Quick C, TopSpeed C and Watcom C (a real loser).

It occurs to me that you might be linking the object modules without
preceding them by a run-time startup module (that sets up the environment,
then invoked main() with appropriate arguments, and after main() returns
invokes exit() etc.).  If the compiler documentation specifies a certain
way of linking, then to assure standard conformance you must follow the
vendor's instructions exactly.