From: sandmann AT clio DOT rice DOT edu (Charles Sandmann)
Message-Id: <9711241629.AA15768@clio.rice.edu>
Subject: Re: Possible enhancements on v2.02
To: eliz AT is DOT elta DOT co DOT il (Eli Zaretskii)
Date: Mon, 24 Nov 1997 10:29:06 -0600 (CST)
Cc: dj AT delorie DOT com, djgpp-workers AT delorie DOT com
In-Reply-To: <Pine.SUN.3.91.971124134758.23713f-100000@is> from "Eli Zaretskii" at Nov 24, 97 01:49:54 pm
Content-Type: text
Precedence: bulk

>      1) Is it a good idea to turn LFN support on Windows 95 *before*
>         DJGPP.ENV is read.  (It will be turned off if DJGPP.ENV says

Yes.  This was the original intent.  The only reason to turn off LFN
behavior is to work around applications which won't work properly 
with it - and hopefully our startup code isn't in that category.

>      2) Should the startup code automatically switch to unixy sbrk
>         when we run on NT?  If there are cases where this would be
>         contrary to user's intentions, we could have a flag that
>         disables this.  (I assume that in most cases, unixy sbrk is
>         the way to go on NT.)

Images should always start as unixy sbrk(), and convert to non-move
only as required by out of memory, nearptr_enable, crt0 flag, or maybe
environment var.  Non-move sbrk() should use variable block sizes to
prevent the out of memory handles problem.