Peter Bex scripsit:
> IMHO, include should do one or the other: relatively to file or the
> current dir, but not both.
C's #include "foo", at least as implemented by gcc, uses the "directory
containing the current file" rule, and I think it makes the most sense.
However, for backward
On Sat, May 28, 2016 at 11:01:56PM +1200, Evan Hanson wrote:
> Hi folks,
>
> Here's another patch for chicken-5. It makes "(include ...)" search for
> files relative to the including file. Relative includes are given the
> lowest search priority, i.e. they are only used when the included file
>
Hi folks,
Here's another patch for chicken-5. It makes "(include ...)" search for
files relative to the including file. Relative includes are given the
lowest search priority, i.e. they are only used when the included file
isn't found in the CWD or any of the directories specified with the
