ZZ>
  >                                                                I have a
  > program that does an "#include " for one of
these new headers.
  > WATCOM found its own  file instead of my  file
  > (which came later in the path).  This, of course, led to errors.
  >
  > Is this acceptable behaviour for a C++ compiler, especially when it is
  > (apparently) undocumented?
ZZ>

  This behaviour is probably due to the fact that the draft C++ standard
  has been altered to remove all of the file extensions from header
  names.

  AFAIAA the standard header names in C++ are now supposed to be

                      
                       
                         
                 

  > JdeBP <
___
 X MegaMail 2.10 #0:
--- Maximus/2 2.02