In a message on 03-12-95, Rob Landley said to Peter Hansen:

> program that does an "#include " for one of
these new headers.

RL>It can add the default extensions for #include ,

You state this as though it were clearly documented.  Is that true?
Where?  AFAIK, this is not standard behaviour for header processing
(since there is no such thing).  In fact, I have seen systems with pairs
of header files like  and  for all standard headers.
Since this is relatively common, it would seem that automatically adding
default extensions for the  form is bad practice.  It is neither
discouraged or encouraged by the standard (well, by Stroustrup).

RL> what you should have done is include "blah".  Quotes, not .
             ^^^^^^
Should?  I've always interpreted the  to mean "search the set of
include directories as defined by the appropriate environment
variable or compiler option" while "blah" to me meant "search the
current directory, then treat as though  were used".  These headers
are not in the current directory since they correspond to library files
that I use in all my applications.  As such, it seems more
appropriate/correct to use  to surround the names.  I use " "
only with application headers.

Nevertheless, I tried out your suggestion and it does work around the
problem.  (Thanks. :-)

I also tried using   (note the trailing period) and that works
as well, though perhaps only on a DOS or OS/2 system.  Does anyone know
how trailing periods are handled in filenames on other systems?  Unix?

------------------------------------------------------------------------
 Peter Hansen                                     Engenuity Corporation
 Internet: peter{at}engcorp.com                    Guelph, Ontario, Canada
---
 * MR/2 *

--- QScan v1.14b / 01-0348