Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Path: utzoo!mnetor!uunet!husc6!cmcl2!brl-adm!brl-smoke!gwyn
From: gwyn@brl-smoke.ARPA (Doug Gwyn )
Newsgroups: comp.lang.c
Subject: Re: What real non-UNIX 'C' compilers implement...
Message-ID: <6445@brl-smoke.ARPA>
Date: Sun, 20-Sep-87 21:32:22 EDT
Article-I.D.: brl-smok.6445
Posted: Sun Sep 20 21:32:22 1987
Date-Received: Mon, 21-Sep-87 03:43:10 EDT
References: <672@sugar.UUCP> <3545@venera.isi.edu> <721@sugar.UUCP>
Reply-To: gwyn@brl.arpa (Doug Gwyn (VLD/VMB) <gwyn>)
Organization: Ballistic Research Lab (BRL), APG, MD.
Lines: 14

The SVID does not attempt to dictate which functions must be
implemented as system calls and which must be implemented as
library routines.  (Contrary to some claims, the SVID is not
simply documentation of one vendor's implementation, but is
a specification for a system interface, very much like POSIX
without any attempt to bless 4.nBSD systems as conforming.)

It made sense to move malloc() into the BA_OS section, even
though it's normally implemented as a library function that
invokes the sbrk() system call (which is not required by the
SVID).  It makes somewhat less sense to have placed STDIO
routines in BA_OS rather than BA_LIB, but since both BA_OS
and BA_LIB are required for Base System conformance, it
really doesn't matter which section they're described in.