From:	jpmorgan AT unm DOT edu (James Paul Morgan)
Subject:	Re: String.h vs string.h bug...
25 Apr 1997 12:48:09 -0700 :
Approved:	cygnus DOT gnu-win32 AT cygnus DOT com
Distribution:	cygnus
Message-ID:	<Pine.A32.3.91.970425103736.61508B-100000.cygnus.gnu-win32@musca.unm.edu>
Mime-Version:	1.0
Original-To:	"Ryan C. Gordon" <rgordon AT vnet DOT net>
Original-cc:	gnu-win32 AT cygnus DOT com
In-Reply-To:	<B7C3D17100@REX.queens.edu>
Original-Sender:	owner-gnu-win32 AT cygnus DOT com

On Fri, 25 Apr 1997, Ryan C. Gordon wrote:

> Very simply, when compiling a C++ program that includes <string.h>, 
> the preprocessor includes <String.h> from the C++ include directory, 
> instead of the (lower case) string.h from the C include dir. This 
> isn't a problem under Unix, I suppose, since "String.h" and 
> "string.h" aren't the same file, but under Windows 95, it's causing 
> problems. Besides annoying warnings of "implicit" declarations of 
> strchr(), I get programs that won't compile due to this error:
> 
The simple workaround is to copy the string.h file to cstring.h and 
then include that instead.  That's what I had to do with the V GUI package.


See ya around the Mulberry bush.

--James

:)

-
For help on using this list (especially unsubscribing), send a message to
"gnu-win32-request AT cygnus DOT com" with one line of text: "help".

- Raw text -