From:	Charles Krug <charles AT pentek DOT com>
Newsgroups:	comp.os.msdos.djgpp
Subject:	Re: <string.h>
Date:	Thu, 12 Feb 1998 16:37:30 -0500
Lines:	27
Message-ID:	<34E36B9A.D8CDDEB1@pentek.com>
References:	<3 DOT 0 DOT 5 DOT 32 DOT 19980211115618 DOT 007ecc60 AT mail DOT kudos DOT net> <34E22910 DOT F245ED05 AT cornell DOT edu> <34E2DB56 DOT 5515BABD AT LSTM DOT Ruhr-UNI-Bochum DOT De> <34E2F36B DOT 37071F81 AT cornell DOT edu> <6bvf9e$65f$1 AT rosenews DOT rose DOT hp DOT com>
NNTP-Posting-Host:	mail.pentek.com
Mime-Version:	1.0
To:	djgpp AT delorie DOT com
DJ-Gateway:	from newsgroup comp.os.msdos.djgpp

Andrew Crabtree wrote:

> A. Sinan Unur wrote in message <34E2F36B DOT 37071F81 AT cornell DOT edu>...
> > AFAIK
> >_string.h (i.e. String.h) is for the GNU String class, as opposed to
> >string which is supposed to be the C++ standard header.

<_string.h>  is the GNU string class, which is documented in info.

<string> is the standard C++ string class, which is the char instantiatiation
of the bastring template class (aren't you glad you asked)  They are similar in
many ways, but NOT identical.  Usually this bites you when you try to assign a
string from a char constant.

I did a project for my data structures class using GNU strings, because I
couldn't figure out the error messages I was getting using stdc++ strings.
Such is the nature of template class errors--you can never figure out just what
the heck they mean.

I DID finally make changes, so that now it will run using either one.



--
Charles Krug, Jr.

- Raw text -