Path: utzoo!utgpu!jarvis.csri.toronto.edu!mailrus!csd4.csd.uwm.edu!cs.utexas.edu!uunet!wuarchive!texbell!sugar!ficc!peter
From: peter@ficc.uu.net (Peter da Silva)
Newsgroups: comp.lang.c
Subject: Re: want to know
Message-ID: <5886@ficc.uu.net>
Date: 25 Aug 89 17:45:21 GMT
References: <8487@bsu-cs.bsu.edu> <2980@solo9.cs.vu.nl> <182@sunquest.UUCP> <THOMAS.89Aug25111034@uplog.uplog.se>
Organization: Xenix Support, FICC
Lines: 15

In article <THOMAS.89Aug25111034@uplog.uplog.se>, thomas@uplog.se (Thomas Hameenaho) writes:
> This is actually a feature. You can do whatever you like in the startup
> code. One example I'm familiar with is for cross-compiling and downloading
> into a standalone system. The startup code initializes the hardware and
> things.

I know a guy who avoided having to write an assembler for a pcode language
by defining the appropriate macros in m4 for as, assembling, linking (to
resolve references), and using the resulting a.out. This would have been,
to say the least, unpleasant if he had to deal with startup code.
-- 
Peter da Silva, *NIX support guy @ Ferranti International Controls Corporation.
Biz: peter@ficc.uu.net, +1 713 274 5180. Fun: peter@sugar.hackercorp.com. `-_-'
"export ENV='${Envfile[(_$-=1)+(_=0)-(_$-!=_${-%%*i*})]}'" -- Tom Neff     'U`
"I didn't know that ksh had a built-in APL interpreter!" -- Steve J. Friedl