Message-ID: <35D29EC0.5936DE45@geocities.com>
From: Merlin <merlin__ AT geocities DOT com>
MIME-Version: 1.0
Newsgroups: comp.os.msdos.djgpp
Subject: Re: malloc()...free()...WTF??
References: <6qr22o$rjn$1 AT birch DOT prod DOT itd DOT earthlink DOT net> <35D158A1 DOT 83BC6888 AT geocities DOT com> <35D22009 DOT 1AA5FA0D AT cs DOT net>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Lines: 23
Date: Thu, 13 Aug 1998 08:10:32 GMT
NNTP-Posting-Host: 238-cy-wpg.ilos.net
NNTP-Posting-Date: Thu, 13 Aug 1998 03:10:32 CDT
Organization: MBnet Networking Inc.
To: djgpp AT delorie DOT com
DJ-Gateway: from newsgroup comp.os.msdos.djgpp
Precedence: bulk



John M. Aldrich wrote:

> Merlin wrote:
> >
> > When you declare a pointer....it doesn't use the 64k which is allocated for
> > variables... so you have to call malloc or calloc to give it a size.. example:
> > int  *a_ptr = (int *)malloc(64000)  //calloc(64000,1) can be used instead of malloc
> > ok...this would make an array-like pointer with 64000 spaces...
>
> Be careful, Merlin... the 64k barrier only exists in 16-bit, real-mode
> compilers; for DJGPP and other 32-bit compilers, the only practical
> limit is the amount of DPMI memory available.
>

oh..right...
sorry..too much turbo pascal for me lately  :)

cya
       Merlin.