🚀 go-pugleaf

This message was sent using a custom form that is not installed on your server.
Some information from the original message may not be displayed. To view the
complete message, ask your network manager to install the form on your server.

In article <41d26q$4vv@engnews2.Eng.Sun.COM>, stephen.clamage@eng.sun.com (Steve
Clamage) wrote:

> Thus, in portable code, you will be able to write for example
> 	#include <iostream>
> and you get the iostream declarations as required by the standard,
> no matter what the implementation provides as files or how it
> spells the file names.
> 
> In addition, an implementation may allow other header spellings to
> mean the same thing. If an implementation previously used
> <iostream.hpp>, it could continue to allow that as a synonym for
> <iostream>. Existing code continues to work unchanged, and standard-
> conforming code also works correctly. I would expect all
> implementations to continue to support their original header spellings
> where they do not conflict with other requirements.

Here's a stupid newbie question about using the standard library C++ headers:
Does this mean I would still have to write `using namespace std' after the
`#include <iostream>', or is such a statement in the header itself? If so, how
can I include this header without importing its symbols directly into the
program?

- Wil Evers (wil@ittpub.nl)


[ comp.std.c++ is moderated.  Submission address: std-c++@ncar.ucar.edu.
  Contact address: std-c++-request@ncar.ucar.edu.  The moderation policy
  is summarized in http://dogbert.lbl.gov/~matt/std-c++/policy.html. ]