Date:	Thu, 29 Oct 1998 19:29:11 +0200 (IST)
From:	Eli Zaretskii <eliz AT is DOT elta DOT co DOT il>
X-Sender:	eliz AT is
To:	djgpp AT delorie DOT com
Subject:	Re: C++ with DJGPP
In-Reply-To:	<gunaalubzrpbz.f1kwom2.pminews@news.avnl1.nj.home.com>
Message-ID:	<Pine.SUN.3.91.981029190123.19933T-100000@is>
MIME-Version:	1.0
Reply-To:	djgpp AT delorie DOT com

On Thu, 29 Oct 1998, Mike Ruskai wrote:

> No, in fact it does not require an extra installation step.  It is already
> the case that someone using long filenames will have to take an extra step to
> configure the compiler for that circumstance.

This extra step goes away in DJGPP v2.02.  There, LFN=y by default, which 
as far as I know should close this problem for good.

The reason the nuisance of having to set LFN=y is still with us is that 
v2.01 was the first version to fix several subtle bugs in LFN support, 
and it seemed a prudent thing at the time to disable it by default.  Add 
to that the relatively long time that passed since v2.01 was released, 
during which many people switched to Windows 9X, and you will see why we 
are where we are now.

But there's no reason to treat that nuisance as something that should 
stay with us.  It won't.

When v2.02 is out, unzipping an archive will produce desired results on 
both LFN and non-LFN platforms automatically.  For that, you must have 
long file names in the zip file, or else you will need to force people to 
use specific unzippers (or risk that they fail to run some script and 
then come back crying).

> I am merely stating that said
> extra step should also remove from the archiver the role of ensuring the
> correct filenames for compiler components.

It's not the unzipper that does that, it's the OS.  DOS itself truncates 
the file names to 8+3 limits when you unzip, and that's how it's supposed 
to work.

> Packaging the program as I've suggested would provide complete functionality
> for normal use.

I'm sorry, I don't see the message with your suggestion, but if LFN is 
enabled by default, what other problems are there that require a 
different method of packaging?

> What possessed you to make such a claim.  This very thread was begun because
> of the fact that '#include  <streambuf.h>' does not in fact work equally well
> with or without long filenames.  

This only happens because LFN is set to N in DJGPP.ENV.  Once v2.02 is 
out, this will go away.

- Raw text -