Message-Id: <9604110841.AA15342@vlsi3>
To: Eli Zaretskii <eliz AT is DOT elta DOT co DOT il>
Cc: djgpp-workers AT delorie DOT com
Subject: Re: Long command lines 
In-Reply-To: Your message of "Thu, 11 Apr 1996 10:48:24 +0200."
             <Pine DOT SUN DOT 3 DOT 91 DOT 960411104107 DOT 27524I-100000 AT is> 
Date: Thu, 11 Apr 1996 01:38:25 -0700
From: Sam Paik <paik AT 3dfx DOT com>

Eli Zaretskii writes:
>
>On Tue, 9 Apr 1996, Sam Paik wrote:
>
>> Is there any particular reason why DJGPP doesn't use a system
>> for long file names compatible with Win95?
>
>IMHO, more info is needed to make such an addition.  Some questions are
>below.
>
>How should a DJGPP program know that it runs in such an environment? 
>Would testing USE_LFN be enough?  Is this a feature of COMMAND.COM that 
>comes with Win95, or of DOS 7.0 in general?  Does COMMAND.COM have any 
>switches to enable or disable this?  If so, how can one know the setting 
>of these switches?

All the information I have on this was derived from the
Win32 SDK documentation that came with MSVC 4.0 followed
by experimentation.  I do not have the answers.  However, I
probably made a typo in the message I sent out:  the information
was for long command lines, not long file names as above.

My interest in this is that I am considering using gnu make
instead of MSVC's nmake, so I went looking for the mechanism
nmake uses to pass long command lines to cl and other 
MSVC tools.

I am not aware of any switches to enable or disable long command
line support, although clearly it is limited by the amount of
environment space available.

Sam