Date: Wed, 18 Jun 2003 18:31:54 +0300
From: "Eli Zaretskii" <eliz AT elta DOT co DOT il>
Sender: halo1 AT zahav DOT net DOT il
To: djgpp-workers AT delorie DOT com
Message-Id: <3405-Wed18Jun2003183154+0300-eliz@elta.co.il>
X-Mailer: emacs 21.3.50 (via feedmail 8 I) and Blat ver 1.8.9
In-reply-to: <3EF00098.5FE616DE@yahoo.com> (message from CBFalconer on Wed, 18
	Jun 2003 02:03:04 -0400)
Subject: Re: nmalloc integration issues: memalign, names
References: <3EECBA0F DOT 9D6D4B30 AT phekda DOT freeserve DOT co DOT uk> <3EECD63E DOT 19C52226 AT yahoo DOT com> <3EEE24E7 DOT E7B03AB0 AT phekda DOT freeserve DOT co DOT uk> <3EEE3821 DOT 2C04E9D4 AT yahoo DOT com> <3EEF6925 DOT 43CCBDBB AT phekda DOT freeserve DOT co DOT uk> <3EEFD834 DOT 45AD84AE AT yahoo DOT com> <2950-Wed18Jun2003064448+0300-eliz AT elta DOT co DOT il> <3EF00098 DOT 5FE616DE AT yahoo DOT com>
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
Precedence: bulk

> Date: Wed, 18 Jun 2003 02:03:04 -0400
> From: CBFalconer <cbfalconer AT yahoo DOT com>
> 
> I can go get that, but what the d*evil am I looking for?

Please look at the functions/problems mentioned by Richard Dawe in
this thread.  If something in what Richard said is unclear, please
don't hesitate to ask for clarifications.

> Where does it end?

I hope the problems mentioned by Richard are the last ones you will
have to deal with, but the truth is I honestly don't know.  Richard
took upon himself to manage the release of DJGPP v2.04--a formidable
job from my experience.  As part of that job, he will discover any
problems in due time.

We told you what we knew at the time, but as Richard integrates
nmalloc into the library and runs tests, he might discover additional
issues, like the ones with memalign.  When that happens, he will raise
the issues and ask you for advice and/or help in resolving them.  That
is how any new significant feature is integrated into DJGPP--via
iterative improvement.

In other words, the fact that new requirements seem to be popping up
is because the additional issues got overlooked when people reviewed
your code.  malloc is central to the library, and memory management is
a notoriously complex issue in the DPMI environment, so I'm not
surprised we are hitting several problems we didn't think about
before; please bear with us a little longer.

> I have no idea how long it will take to implement.

Please download the CVS snapshot from the URL I mentioned, look at
memalign.c, and let's talk afterwards if the implementation suitable
for nmalloc doesn't readily present itself.  Okay?

> And what about those other things, vmalloc, mmap, whatever?

valloc is imlpemented as a simple wrapper on top of memalign, so once
you figure out memalign, valloc is not an issue.

As for mmap, I don't think we have it, so don't worry about it.

TIA