> In mach, -D defines were essentially not used.  Config would put each
> define into its own .h file.  This means that all source files must
> explicitly include the .h's which set defines that they care about.
> But it also means that if the define is changed, the header file is
> changed, and the dependency process takes over to regenerate the .o
> files that need to be changed.

This sounds neat, but how could this work?  config would need to know
about every define ever used anywhere, so that it would know to create
empty .h files for absent defines.  Maintaining this central list of
defines would be almost more of a headache than having to manually blow
away .o files when you change something that ends up in a -D option.

Or so it seems to me.  What am I missing?

					der Mouse

			    mouse@collatz.mcrcim.mcgill.edu
		    01 EE 31 F6 BB 0C 34 36  00 F3 7C 5A C1 A0 67 1D