On Sat, Mar 04, 2000 at 03:52:39PM -0700, John Starkey wrote:
> > It shouldn't make a differnce. g++ keeps header files in
> > /usr/include/g++-<1 or 2 or 3>/
> >
> > and the entire non-comment section of iostream
> > is
> >
> > #ifndef __IOSTREAM__
> > #define __IOSTREAM__
> > #include <iostream.h>
> > #endif
>
> So all it's doing is referring it to iostream.h??
>
> Why did that get started. That many people forgetting the h???
>
Probably because it is in the standard. The actual ANSI
standard costs a lot of money, but you can look at the
1996 working papers which are pretty close at:
http://www.cs.rpi.edu/~musser/ap/c++std/cd2/
Specifically
http://www.cs.rpi.edu/~musser/ap/c++std/cd2/lib-iostreams.html#lib.iostream.objects
which states that the header <iostream>(no h) will give you such
and so....
I would guess this didn't get dropped when they made the ANSI
standard, but I'm not certain here (I'll find out if you'll buy
me a copy :-) ).
> > Which is a header trick that seems to be more common to c++, that makes
> > the file empty if it's already been included. (Think headers that include
> > headers).
> > But it still seems kind of odd to me, since iostream.h already
> > wraps itself in _IOSTREAM_H . Maybe ANSI c++ says you should be able
> > to do #ifdef __IOSTREAM__ to check for iostream.
>
> I keep hearing about wrappers in the linux environ. What is the definition??
>
Wrappers are often scripts that set up environment variables
and find locations of files, so that when the actual program
runs, it can find what it neeeds. The debian adobe acrobat
is like this, so is Star Office. ~/Office/bin/soffice is a shell
script. I can't think of another off the top of my head.
I was just saying that it wraps itself is #ifndef's to prevent
multiple inclusion.
Again, have you gotten your C++ program to compile?
have fun,
greg
--
this is not here
-
To unsubscribe from this list: send the line "unsubscribe linux-newbie" in
the body of a message to [EMAIL PROTECTED]
Please read the FAQ at http://www.linux-learn.org/faqs
