* Re: [?] iostream vs. iostream.h
@ 1998-01-30 16:29 Chris Dern
0 siblings, 0 replies; 2+ messages in thread
From: Chris Dern @ 1998-01-30 16:29 UTC (permalink / raw)
To: Houssam Moustafa, egcs
Please correct me if i'm wrong, but here is my understanding.
the iostream include, is the new convention, when using namespace.
As far as I know, both gcc and egcs don't support this yet. However to
"ease" the
transition into the new convention. gcc includes iostream, yet if you look
at it, I believe that it just includes iostream.h for now.
Chris
----------
> From: Houssam Moustafa <hmoustafa@bridge.com>
> To: egcs@cygnus.com
> Subject: [?] iostream vs. iostream.h
> Date: Friday, January 30, 1998 11:10 AM
>
> stroustrup's 3rd ed. only includes "iostream", not "iostream.h".
>
> so how come egcs 1.0 and gcc 2.8.0 have both "iostream" and
> "iostream.h", but egcs 1.0.1 only has "iostream.h"?
>
> houssam
^ permalink raw reply [flat|nested] 2+ messages in thread
* [?] iostream vs. iostream.h
@ 1998-01-30 11:12 Houssam Moustafa
0 siblings, 0 replies; 2+ messages in thread
From: Houssam Moustafa @ 1998-01-30 11:12 UTC (permalink / raw)
To: egcs
stroustrup's 3rd ed. only includes "iostream", not "iostream.h".
so how come egcs 1.0 and gcc 2.8.0 have both "iostream" and
"iostream.h", but egcs 1.0.1 only has "iostream.h"?
houssam
^ permalink raw reply [flat|nested] 2+ messages in thread
end of thread, other threads:[~1998-01-30 16:29 UTC | newest]
Thread overview: 2+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
1998-01-30 16:29 [?] iostream vs. iostream.h Chris Dern
-- strict thread matches above, loose matches on Subject: below --
1998-01-30 11:12 Houssam Moustafa
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).