From: Al Christians <achrist AT easystreet DOT com>
Newsgroups: comp.os.msdos.djgpp
Subject: Re: Template/STL questions
Date: Thu, 13 Aug 1998 10:00:03 -0700
Organization: Trillium Resources Corporation
Lines: 20
Message-ID: <35D31B93.336D@easystreet.com>
References: <35D24762 DOT 7E27 AT easystreet DOT com> <35D2EB5D DOT C1AF7939 AT pentek DOT com>
Reply-To: achrist AT easystreet DOT com
NNTP-Posting-Host: dial-56-175.easystreet.com
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
NNTP-Posting-Date: 13 Aug 1998 16:51:24 GMT
To: djgpp AT delorie DOT com
DJ-Gateway: from newsgroup comp.os.msdos.djgpp
Precedence: bulk

Charles Krug wrote:
> 
> One problem that can come up with <string> is that djgpp comes with two
> string classes:  The STL string template class, and the GNU string class.
> Using calls into one when you mean the other can have "unpredictable and
> undesirable" (tm) results.
> 
> I had similar troubles last year when I was learning my way around C++,
> with much the same symptoms.
> 

Thanks for the pointer.  I think you got it.  How else could " a
string;"
not produce an empty string unless some other contructor than the one in
bstring is getting called?   We've got "#include <string>" everywhere,
except
one place in our rendition of zlib, theres an "#include <string.h>".  Is
that the gotch that gotcha?

Al