Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!sdd.hp.com!zaphod.mps.ohio-state.edu!lavaca.uh.edu!menudo.uh.edu!sugar!ficc!peter
From: peter@ficc.ferranti.com (Peter da Silva)
Newsgroups: comp.std.c
Subject: Re: Frustrated trying to be portable
Keywords: ANSI C, standard library
Message-ID: <.OR9O.C@xds13.ferranti.com>
Date: 27 Feb 91 17:12:48 GMT
References: <1991Feb17.203337.20569@uokmax.ecn.uoknor.edu> <2956@cirrusl.UUCP> <4108@lupine.NCD.COM> <15333@smoke.brl.mil>
Reply-To: peter@ficc.ferranti.com (Peter da Silva)
Organization: Xenix Support, FICC
Lines: 15

> It isn't necessary.  If the application requires library functions
> that are required for a hosted implementation but not for a
> freestanding implementation, then it couldn't survive being told
> that it is being compiled by a freestanding implementation anyway.

---------- complex_utility_routine.c
#ifdef HOSTED
	compile a bunch of journalling code for debugging in
	the hosted version
#else
	compile a bunch of stubs
#endif
-- 
Peter da Silva.  `-_-'  peter@ferranti.com
+1 713 274 5180.  'U`  "Have you hugged your wolf today?"