🚀 go-pugleaf

Hi,
Michael Cook (mcook@cognex.com) wrote:
: >>>>> "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?

Yes, there was some rule "like" this: In clause 'D' which describes
compatibility features (actually in depr.c.headers).  However, this
section _ONLY_ covers headers inherited from C all ending with '.h'.
These header files are also replaced:  'header.h' is replaced by
'cheader' where 'header' stands as a placeholder for any of the C
header files (I first used 'foo' instead of 'header' but it would have
been a misnomer :-) This section does not mandate such a compatibility
header for any of the existing C++ header files.
--
dietmar.kuehl@uni-konstanz.de
http://www.informatik.uni-konstanz.de/~kuehl
I am a realistic optimist - that's why I appear to be slightly pessimistic


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