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 compatibility it would make sense to me to look in $PWD next before looking in the standard include path. > An include-relative is defined by the s48-modules egg. I think it > makes more sense to have that, especially considering we also have > load-relative. Good point. -- John Cowan http://www.ccil.org/~cowan co...@ccil.org Tautology is something that is tautological. --Francois-Rene Rideau _______________________________________________ Chicken-hackers mailing list Chicken-hackers@nongnu.org https://lists.nongnu.org/mailman/listinfo/chicken-hackers
