From: firewind <firewind AT metroid DOT dyn DOT ml DOT org>
Newsgroups: comp.os.msdos.djgpp
Subject: Re: Memory allocation
Date: 7 Nov 1997 03:10:16 GMT
Organization: Netcom
Lines: 26
Message-ID: <63u0qo$rn9@sjx-ixn5.ix.netcom.com>
References: <97Nov6.200722gmt+0100 DOT 11649 AT internet01 DOT amc DOT de>
NNTP-Posting-Host: elp-tx3-22.ix.netcom.com
Mime-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 8bit
To: djgpp AT delorie DOT com
DJ-Gateway: from newsgroup comp.os.msdos.djgpp
Precedence: bulk

Christopher Croughton <crough45 AT amc DOT de> wrote:
> How standard is the sbrk(2) function?  It's on every Unix I've seen,
> and appears to be in DJGPP as well, but it's not as far as I can tell 
> ANSI.  How much can I rely on it being there, and is using it likely
> to mess up malloc etc.?  Does it actually work under DJGPP as it does
> in Unix?

'man sbrk' on my Linux system yields:

CONFORMING TO
       BSD 4.3

       brk and sbrk are not defined in the  C  Standard  and  are
       deliberately excluded from the POSIX.1 standard (see para-
       graphs B.1.1.1.3 and B.8.3.3).


sbrk() appears to do the same thing on either Linux or DJGPP from their
descriptions, but I can't conceive of any way to verify this.

-- 
[-                               firewind                                   -]
[-   email: firewind AT metroid DOT dyn DOT ml DOT org (home), firewind AT aurdev DOT com (work)  -]
[-          "You're just jealous because the voices talk to -me-."          -]
[-                   Have a good day, and enjoy your C.		            -]
[-          (on a crusade of grumpiness where grumpiness is due)            -]