Path: utzoo!censor!geac!torsqnt!news-server.csri.toronto.edu!cs.utexas.edu!wuarchive!zaphod.mps.ohio-state.edu!samsung!uunet!taumet!steve
From: steve@taumet.com (Stephen Clamage)
Newsgroups: comp.std.c
Subject: Re: Frustrated trying to be portable
Message-ID: <608@taumet.com>
Date: 20 Feb 91 16:52:42 GMT
References: <1991Feb17.203337.20569@uokmax.ecn.uoknor.edu> <15240@smoke.brl.mil> <4188@skye.ed.ac.uk>
Organization: Taumetric Corporation, San Diego
Lines: 17

richard@aiai.ed.ac.uk (Richard Tobin) writes:

|As far as I can tell, some of the library functions described in the
|standard can be implemented portably ... whereas some others can't....

|A compiler that provided only the non-portably-implementable library
|functions (and headers) might well be very useful in a hosted
|environment.

Why would it be useful?  If you wanted to use the remainder of the
standard functions, you would have to write or acquire source for them,
or hope that their implementation in the binary library supplied with
some other compiler would work.  I fail to see a market for such a
grossly incomplete implementation.
-- 

Steve Clamage, TauMetric Corp, steve@taumet.com