Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!sdd.hp.com!wuarchive!csus.edu!beach.csulb.edu!nic.csu.net!csun!kithrup!sef
From: sef@kithrup.COM (Sean Eric Fagan)
Newsgroups: comp.lang.c
Subject: Re: Whose code should we break? ( was Re: 64 bit C )
Message-ID: <1991Feb20.050525.6515@kithrup.COM>
Date: 20 Feb 91 05:05:25 GMT
References: <1215@dms.UUCP> <65469@brunix.UUCP> <11285@pasteur.Berkeley.EDU>
Distribution: comp.arch
Organization: Kithrup Enterprises, Ltd.
Lines: 20

In article <11285@pasteur.Berkeley.EDU> jbuck@galileo.berkeley.edu (Joe Buck) writes:
>Use size_t.  This is a typedef which is in /usr/include/sys/types.h on
>most Unix systems.  ANSI C requires every C implementation to provide
>a definition for it.  It must evaluate to an integral type big enough
>to hold a pointer.

Right.  Sure.  I see you've actually read anything Doug has ever posted
about the subject.

(that was extreme sarcasm, for those who weren't here when I typed it.)

size_t is an integral type *big enough to hold the size of any single
object*.  On a '286, for example, with a 16Mb address space, size_t should
be int, not long.

-- 
Sean Eric Fagan  | "I made the universe, but please don't blame me for it;
sef@kithrup.COM  |  I had a bellyache at the time."
-----------------+           -- The Turtle (Stephen King, _It_)
Any opinions expressed are my own, and generally unpopular with others.