This is the mail archive of the
cygwin@sourceware.cygnus.com
mailing list for the Cygwin project.
RE: <string.h> .vs. <String.h>
- To: shankar at chromatic dot com
- Subject: RE: <string.h> .vs. <String.h>
- From: dahms at ifk20 dot mach dot uni-karlsruhe dot de
- Date: Fri, 31 Jan 1997 03:42:33 EST
- CC: gnu-win32 at cygnus dot com, dahms at ifk20 dot mach dot uni-karlsruhe dot de
Hi, you wrote:
: Technically, the ANSI C++ committee is off the hook, because they have
: mandated that C++ include files be included simply as <String>,
: <iostream>, etc., and so it should be possible to distinguish between
: <String> and <string.h>.
I have never heard about the .h-less includes!
: In practice, however, 100% of all C++ installations still ship their
: files using a .h suffix, and we have a clash. Remember that ANSI C++
: still grandfathers in the <string.h> file from C, so we have a situation
: in which C++ implementations have to ship both files, and given the
: case-insensitive nature of many file systems, they have a problem on
: their hands.
Would it be possible having *identical* contents for both, depending
on _CPLUSPLUS or some such, protected from multiple includes by the same
ifdef, or both just including another, third file with a secure name?
Bye, Heribert (dahms@ifk20.mach.uni-karlsruhe.de)
-
For help on using this list, send a message to
"gnu-win32-request@cygnus.com" with one line of text: "help".