🚀 go-pugleaf

Michael Cook <mcook@cognex.com> writes:

>>>>>> "SC" == Steve Clamage <clamage@Eng.Sun.COM> writes:

> SC> if a compiler previous used <iostream.hxx>, I would expect it to continue
> SC> to accept <iostream.hxx>, and pick up the same header file as <iostream>.

>Wasn't there some rule about `#include <foo>' being treated like `#include
><foo.hxx>' followed by a bunch of `using' declarations?

No. You are probably thinking of the two forms of the headers which
are inherited from Standard C. For example,
	<stdlib.h> and <cstdlib>
	<stdio.h>  and <cstdio>
	<string.h> and <cstring>
	... etc ...
The <cxxx> form corresponding to <xxx.h> puts all the declarations in
the "std" namespace. The <xxx.h> form, the form used in C, has those
same declarations in "std" followed by using-declarations for each
item. Thus, when you include <stdio.h>, the effect on the program
is the same as in a C program. If instead you include <cstdio>,
you can select the declarations you want by qualifying them explicitly
or by employing individual using-declarations, or you could get all
of them via a "using namespace std" directive.

The standard headers specific to C++ have only one form defined in
the standard, such as <new>, <iostream>, and so on. An implementation
can supply whatever additional headers it likes, with whatever
semantics it likes.
--
Steve Clamage, stephen.clamage@eng.sun.com


---
[ 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. ]