Mail Archives: djgpp/2000/01/30/19:03:47
Manni Heumann wrote:
>
> In article <E1D0A4CADBAC5FC0 DOT 8E50956E4A580C85 DOT 79A2A03D8020D9D0 AT lp DOT airnews DOT net>, Rodeo Red <rodeored AT netstep DOT net> wrote:
> >Manni Heumann wrote:
> >>
> >> Standard headers in C++ don't come with a suffix.
> >> libgpp should not be necessary for C++, you only need it to compile legacy
> >> code (e.g. to compile programs that use the String class).
> >>
> >> But what sort of functionality should <ostream> contain?
> >
> >It opens a file for output. from my text books it seems to be part of
> >the standard library.
> >AFAIK, that measn it should be in djgpp and I probably lost it. It
> GCC may not be fully compliant to the C++ standard. But in this case it won't
> keep you from writing standard compliant code.
>
Thanks for helping- I think you're right to say I could get the code to
work without ostream. (There's more mentions of ostrean than just rhe
call to the header, so I'll have to do more than delete "#include
<ostream>". Still what I would really like to know is; is ostream is
supposed to be in djgpp, or did I just lose it ?
You seem to be saying it may not come with djgpp, but I find this hard
to believe, and I'd like to know for sure. My understanding is that
dgjpp should contain it, but since I'm new to this, I could definitely
be wrong.
Can anyone find ostream in their copy of djgpp ?
Can anyone not find it ?
Am I asking too much or something ? It seems like such a simple
question.
Red
- Raw text -