Path: utzoo!mnetor!tmsoft!torsqnt!news-server.csri.toronto.edu!cs.utexas.edu!sdd.hp.com!elroy.jpl.nasa.gov!decwrl!deccrl!news.crl.dec.com!decvax.dec.com!ima!dirtydog!karl
From: karl@ima.isc.com (Karl Heuer)
Newsgroups: comp.lang.c
Subject: Re: Can Novices Jump Directly in C? (Books)
Message-ID: <1991Feb13.031702.16513@dirtydog.ima.isc.com>
Date: 13 Feb 91 03:17:02 GMT
References: <ENAG.91Feb8021615@holmenkollen.ifi.uio.no> <11929@helios.TAMU.EDU> <1991Feb9.042957.20160@athena.mit.edu> <427@bria> <KERS.91Feb11094224@cdollin.hpl.hp.com>
Sender: news@dirtydog.ima.isc.com (NEWS ADMIN)
Reply-To: karl@ima.isc.com (Karl Heuer)
Organization: Interactive Systems
Lines: 19

In article <KERS.91Feb11094224@cdollin.hpl.hp.com> kers@hplb.hpl.hp.com (Chris Dollin) writes:
>mike@bria writes:
>>To write portable code, the use of values.h and sys/types.h is essential,
>
>Use "values.h" or "sys/types.h" on *my* machine [*1], and your code won't
>compile at all; I have a plain ANSI C compiler, and neither of those names
>appear to be in the standard.
>
>Is their general agreement on the contents of these headers...?

<sys/types.h> is defined by the POSIX standard.  Types that are useful to a
pure ANSI C program are already defined in ANSI headers (e.g. time_t in
<time.h>), so there's no need for <sys/types.h> here.  And you should use
<limits.h> rather than <values.h> if you want portability.%

Karl W. Z. Heuer (karl@ima.isc.com or uunet!ima!karl), The Walking Lint
________
% Even on a pre-ANSI system.  There are PD configuration tools that will
  build <limits.h> for you.