Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!usc!sdd.hp.com!decwrl!bacchus.pa.dec.com!shlump.nac.dec.com!tkou02.enet.dec.com!diamond
From: diamond@tkou02.enet.dec.com (diamond@tkovoa)
Newsgroups: comp.lang.c
Subject: Re: Turbo C large character array
Message-ID: <1897@tkou02.enet.dec.com>
Date: 7 Aug 90 02:32:27 GMT
References: <14260@shlump.nac.dec.com> <manning.649959245@coil>
Reply-To: diamond@tkou02.enet.dec.com (diamond@tkovoa)
Distribution: comp
Organization: Digital Equipment Corporation Japan , Tokyo
Lines: 12

In article <manning.649959245@coil> manning@coil.caltech.edu (Evan Marshall Manning) writes:

>I believe malloc() takes size_t = unsigned int.  On systems where int is
>16 bits 64K is indeed the limit.

size_t = unsigned some_integral_type.  On systems where int is 16 bits, size_t
might be 128 bits although the limit might be 2**64 instead of 2**128.  On
systems where int is 64 bits, size_t might be 32 bits.  If you want to know
the limit on your machine, you have to RTFM.  Calculations will not tell you.
-- 
Norman Diamond, Nihon DEC     diamond@tkou02.enet.dec.com
This is me speaking.  If you want to hear the company speak, you need DECtalk.