In article 94Sep1092612@physics2.berkeley.edu, matt@physics2.berkeley.edu (Matt Austern) writes:
>In article <rfgCvFxwp.852@netcom.com> rfg@netcom.com (Ronald F. Guilmette) writes:
>
>> Is Borland the only compiler that fails to do this in the manner to which
>> I have become accustomed?  (I have yet to find any others which refuse to
>> even look for the include file in the same directory as the file doing the
>> including when the double-quoted form of the #include directive is used.)
>
>I think so.  It's the only compiler I've seen, anyway, that behaves
>this way.
>
>I can't really call it a bug, of course: their compiler works as
>documented, and it is standard-conforming.

VAX C has always had the rule that searches start in the directory containing
the top-level file, independent of where the "current" file is located. So
Borland is not alone in being different :-)

Yet another annoyance when moving source code among Unix, DOS, and VAX/VMS.

---
Steve Clamage, stephen.clamage@eng.sun.com