Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Path: utzoo!utgpu!water!watmath!clyde!burl!codas!killer!academ!uhnix1!sugar!peter
From: peter@sugar.UUCP
Newsgroups: comp.lang.c
Subject: Re: What real non-UNIX 'C' compilers implement...
Message-ID: <721@sugar.UUCP>
Date: Mon, 14-Sep-87 12:00:49 EDT
Article-I.D.: sugar.721
Posted: Mon Sep 14 12:00:49 1987
Date-Received: Sat, 19-Sep-87 07:25:45 EDT
References: <672@sugar.UUCP> <3545@venera.isi.edu>
Organization: Sugar Land UNIX - Houston, TX
Lines: 20
Summary: System V braindamage.

In article <3545@venera.isi.edu>, lmiller@venera.isi.edu (Larry Miller) writes:
> The problem goes beyond just read and write, to any OS system calls.  The
> new Turbo C makes things worse because, unlike UNIX which separates system
> calls (Section 2 in the manual) from C library routines (Section 3), Turbo
> C just gloms them all in alphabetical order in the reference manual.  NO
> new programmer to C would have any inclination that some calls are portable
> C, and some are DOS specific.

AT&T manuals now puts some of the library routines into the system call
section. For some bizzarre reason fclose, fflush, fopen, freopen, fdopen,
fread, fseek, rewind, ftell, fwrite, malloc, free, popen, and system are
in "Base System Routines" (which seems to be mostly section 2)... rather
than being in "standard library routines" (section 3).

So, UNIX isn't nice and elegant anymore.

(System V... from now on, consider it substandard)
-- 
-- Peter da Silva `-_-' ...!hoptoad!academ!uhnix1!sugar!peter
--                 'U`      ^^^^^^^^^^^^^^ Not seismo!soma (blush)