Re: While compiling gwp...

[Gleef <dzol virtual-yellow com>]

On Sun, 10 Jan 1999, Ian Peters wrote:
> On Sun, Jan 10, 1999 at 10:57:10AM -0600, Havoc Pennington wrote:
> > 
> > On Sun, 10 Jan 1999, Ian Peters wrote:
> > > htmlIO.C:20: iostream.h: No such file or directory
> > > 
> > > Where do I find this, why am I missing this, etc.?
> > > 
> > 
> > In the latest C++ standard it's just <iostream>, no .h. <iostream.h> is 
> > sort of a relic that g++ happens to have laying around. So if you're not
> > using g++, maybe try changing it to <iostream> and see if it works.
> > 
> > Havoc
> 
> A quick check shows that I have libstdc++-2.8.0, egcs-c++-1.0.3a, and
> libg++-2.7.2.8 installed, but locate iostream shows nothing.  Hrrm.

FYI:

In RedHat: 
  $ rpm -q libstdc++-devel
  libstdc++-devel-2.8.1-2
  $ rpm -ql libstdc++-devel |grep iostream
  /usr/include/g++/iostream
  /usr/include/g++/iostream.h
  /usr/include/g++/stdiostream.h
  /usr/info/iostream.info.gz

In RedHat 5.0:
  $ rpm -qlp libg++-devel-2.7.2.8-6.i386.rpm |grep iostream
  /usr/include/g++/iostream.h
  /usr/include/g++/stdiostream.h
  /usr/info/iostream.info-1.gz
  /usr/info/iostream.info-2.gz
  /usr/info/iostream.info.gz

In RedHat 5.1:
  $ rpm -qlp libstdc++-devel-2.8.0-8.i386.rpm
  /usr/include/g++/iostream
  /usr/include/g++/iostream.h
  /usr/include/g++/stdiostream.h

So it looks like iostream.h is the safer choice in RedHat.  Also, since
these packages are based on the same GNU tarballs other distributions use,
I would assume iostream.h would be safest for Linux in general.

Of course, since "Standard C++" is pretty much an oxymoron, other
platforms might deviate greatly.  Most documentation I have seen uses
"#include <iostream.h>" rather than "#include <iostream>".  I have also
seen systems where you use "#include <iostream.hpp>" or "#include
<stream.h>" instead.

-Gleef