Path: utzoo!utgpu!news-server.csri.toronto.edu!rpi!zaphod.mps.ohio-state.edu!sol.ctr.columbia.edu!lll-winken!uunet!taumet!steve
From: steve@taumet.com (Stephen Clamage)
Newsgroups: comp.std.c
Subject: Re: ANSI C standard library
Message-ID: <681@taumet.com>
Date: 20 Apr 91 22:18:08 GMT
References: <1991Apr11.185038.108@cpqhou.uucp> <1991Apr15.194430.18673@webo.dg.com> <677@taumet.com> <1991Apr20.092845.14164@watdragon.waterloo.edu>
Organization: Taumetric Corporation, San Diego
Lines: 17

ccplumb@rose.waterloo.edu (Colin Plumb) writes:

>- A large fraction of the ANSI C library can't be written in *strictly
>conforming* ANSI C.  This was usually the reason of putting it in the
>library in the first place - without the library function, the programmer
>would be up the creek.  Thus, if you want a strictly conforming (guaranteed
>to work on any ANSI C compiler) C library, you're out of luck.

In the full posting you mentioned only setjmp and longjmp as
functions which cannot be written in strictly-conforming C, and
memmove which cannot be written efficiently in strictly-conforming C.
Can you name any other functions in the standard C library which
cannot reasonably be written in strictly-conforming C, or does 2%
(3 out of about 150) constitute a "large fraction"?
-- 

Steve Clamage, TauMetric Corp, steve@taumet.com