[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: single vs. multi-sexp modules

Jim Blandy wrote:
> In other words, [the C standard] leaves it entirely implementation-defined how the
> header names are interpreted, and where the referenced files are
> stored.

For instance, on an old, very strict ANSI C compiler for RISC OS, if you
had a globals.h and a main.c, you'd structure your project with one "h"
directory containing a file named "globals", and one "c" directory
containing a file named "main", because "." is the directory separator
on RISC OS! (Porting to that compiler was an enormous pain in the