Date:	Wed, 18 Apr 2001 15:51:13 -0400
Message-Id:	<200104181951.PAA02208@envy.delorie.com>
X-Authentication-Warning:	envy.delorie.com: dj set sender to dj AT envy DOT delorie DOT com using -f
From:	DJ Delorie <dj AT delorie DOT com>
To:	djgpp AT delorie DOT com
In-reply-to:	<3ADDEDBF.A0A004BF@yahoo.com> (message from Outsider on Wed, 18
	Apr 2001 21:40:47 +0200)
Subject:	Re: Why the deception?
References:	<3ADDEDBF DOT A0A004BF AT yahoo DOT com>
Reply-To:	djgpp AT delorie DOT com
Errors-To:	nobody AT delorie DOT com
X-Mailing-List:	djgpp AT delorie DOT com
X-Unsubscribes-To:	listserv AT delorie DOT com

> Below are the file lists I got from the zip picker page for
> MS-DOS. They are filled with illegal file names, to wit:
> 
> bin/addr2line.exe
> info/binutils.info
> info/gasp.info
> info/gprof.info
> bin/unprotoize.exe
> lang/cxx/algorithm
> lang/cxx/builtinbuf
> lang/cxx/indstream
> lang/cxx/stlhashmap

None of these are illegal on DOS.  DOS will gladly create files when
asked to using these names, and quietly chop off the characters it
won't support.  Nothing wrong with that; it's intentional.  DJGPP zip
files offer the full name for DOS machines supporting the long file
name standard (like, DOS with LFNDOS installed), so that *if* the full
name can be preserved, it will be, else programs ported from Unix will
be confused.

> How about ANSI/ISO C++ for DOS, where is it?
> How about ANSI/ISO C++ for Win3.1x, where is it?

DJGPP followed the ANSI/ISO specs as closely as GCC does.  We're not
GCC engineers.  If you have a problem with GCC's compliance to
standards, you'll need to take it up on the GCC list.  I strongly
suggest you find out if gcc already follows the standards before
accusing them of anything, though.  I suspect it already does.

- Raw text -