Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Path: utzoo!utgpu!water!watmath!clyde!rutgers!sunybcs!boulder!hao!oddjob!gargoyle!ihnp4!homxb!mtuxo!mtune!codas!killer!academ!uhnix1!sugar!peter
From: peter@sugar.UUCP
Newsgroups: comp.lang.c
Subject: why "gmtime" but not "read" and "write"?
Message-ID: <706@sugar.UUCP>
Date: Sat, 12-Sep-87 09:14:58 EDT
Article-I.D.: sugar.706
Posted: Sat Sep 12 09:14:58 1987
Date-Received: Sat, 19-Sep-87 06:46:45 EDT
Organization: Sugar Land UNIX - Houston, TX
Lines: 13

Y'all are missing the point. Why include "gmtime" and "localtime" in Ansi-C
(other than to keep the well known false sense of well-being when trying to
port UNIX programs to non-UNIX systems), but leave read/write/etc out? It
just doesn't seem consistent to me. Since most non-UNIX-based 'C' compilers
in the real world implement read and write and *not* gmtime and localtime,
you don't even have precedent behind you.

Don't get me wrong... I like having gmtime and localtime around.

I just think there's a place for read and write as well.
-- 
-- Peter da Silva `-_-' ...!hoptoad!academ!uhnix1!sugar!peter
--                 'U`      ^^^^^^^^^^^^^^ Not seismo!soma (blush)