This is the mail archive of the
libstdc++@gcc.gnu.org
mailing list for the libstdc++ project.
Re: <iosfwd> also standard for std::string declaration?
- From: landrum Alfred <alfred137 at yahoo dot com>
- To: libstdc++ at gcc dot gnu dot org
- Cc: alfred137 at yahoo dot com
- Date: Tue, 17 Jun 2003 15:07:59 -0700 (PDT)
- Subject: Re: <iosfwd> also standard for std::string declaration?
Ok, I just did. On the Athlon 1800 I'm using, the
difference between including <string> & not is about
300 milliseconds. Not that much, I admit. :)
I started looking at this because I noticed how big of
a jump in size the .i's had before & after the
<string> inclusion - about 300k difference.
Hmm. Well, just for completeness sake, is there a
standard way of getting a string declaration?
--- Nathan Myers <ncm-nospam@cantrip.org> wrote:
> On Tue, Jun 17, 2003 at 02:23:15PM -0700, landrum
> Alfred wrote:
> > I'm trying to reduce my compile times. I have
> several
> > headers that are including <string>, even though
> they
> > only need a declaration.
> >
> > I noticed that <iosfwd> on my RH8 box includes
> > bits/stringfwd.h.
> >
> > Does this imply that including <iosfwd> is a
> standard
> > way to get a forward declaration of std::string?
>
>
> No, it's a non-standard way. BTW, have you measured
> a difference?
>
> Nathan Myers
> ncm-nospam@cantrip.org
__________________________________
Do you Yahoo!?
SBC Yahoo! DSL - Now only $29.95 per month!
http://sbc.yahoo.com