From:	"Tim Van Holder" <tim DOT van DOT holder AT pandora DOT be>
To:	<djgpp-workers AT delorie DOT com>
Subject:	RE: Interest in Smalltalk and/or Python?
Date:	Sun, 14 Jan 2001 20:46:05 +0100
Message-ID:	<NEBBIOJNGMKPNOBKHCGHMEJJCAAA.tim.van.holder@pandora.be>
MIME-Version:	1.0
X-Priority:	3 (Normal)
X-MSMail-Priority:	Normal
X-Mailer:	Microsoft Outlook IMO, Build 9.0.2416 (9.0.2910.0)
In-Reply-To:	<8011-Sun14Jan2001203735+0200-eliz@is.elta.co.il>
Importance:	Normal
X-MimeOLE:	Produced By Microsoft MimeOLE V5.50.4133.2400
X-MIME-Autoconverted:	from quoted-printable to 8bit by delorie.com id OAA29711
Reply-To:	djgpp-workers AT delorie DOT com
Errors-To:	nobody AT delorie DOT com
X-Mailing-List:	djgpp-workers AT delorie DOT com
X-Unsubscribes-To:	listserv AT delorie DOT com

> > Annoyance! As it turns out, the latest smalltalk package requires mmap(),
> What does it use mmap for?  Does it really want memory-mapped files,
> or is that just for better memory allocation?
Seems to be just memory allocation; it has a new source file (heap.c) that
provides memory allocation. I've added some ifdef's to the only file using
it; if HAVE_MMAP is 0, it uses the 'old' memory allocation from 1.7.0.
I still need to test this though; let's hope both methods are compatible.

- Raw text -