On Monday, John Cowan wrote:
>
> If I were an implementer, I'd do what gcc does: look in the
> directory of the including file, then in a list of user-specified
> places, then in a list of implementation-specified places.

Include files in GCC are used for things like system-wide
configuration, where a user-defined search path makes sense.
`include' is used for plain code, so the C analogy is closer to an
`#include "foo.h"'.  But even that is not close enough to `include' to
draw any conclusions: in the majority of use cases you'd want to
include a specific file just once whereas in C the majority of uses is
including files many times.

--
          ((lambda (x) (x x)) (lambda (x) (x x)))          Eli Barzilay:
                    http://barzilay.org/                   Maze is Life!

_______________________________________________
Scheme-reports mailing list
Scheme-reports@scheme-reports.org
http://lists.scheme-reports.org/cgi-bin/mailman/listinfo/scheme-reports