Xref: news2.mv.net comp.os.msdos.djgpp:3576
From: Charles Sandmann <sandmann AT clio DOT rice DOT edu>
Newsgroups: comp.os.msdos.djgpp
Subject: Re: Lots of Q's
Date: Wed, 08 May 1996 08:15:06 CDT
Organization: Rice University, Houston, Texas
Lines: 7
Message-ID: <31909e5a.sandmann@clio.rice.edu>
References: <199605071216 DOT IAA00745 AT mv DOT mv DOT com>
Reply-To: sandmann AT clio DOT rice DOT edu
NNTP-Posting-Host: clio.rice.edu
To: djgpp AT delorie DOT com
DJ-Gateway: from newsgroup comp.os.msdos.djgpp

> once non-unix sbrk is the default, does that mean nothing will change the
> program's linear base? I.e. near pointers without recalculation are safe? 

Yes, that's one of the advantages behind using the non-move/non-unix sbrk()
algorithm.  It really works out fairly well - programs that expect a unix-like
sbrk() probably aren't hooking interrupts and using near pointers to video,
which are the two things the unix sbrk() doesn't do well.