On Wed, 2 Jul 1997, Peter Gerwinski wrote:
I don't agree. The *name* of the executable can be considered part of the program. The *path* where it will be stored will be system dependent, so the path, IMHO, does not belong into the source, but on the commandline (or into a (system or user or project specific) config file, of course).
A directive (*$Foo="Bar"*) is always equivalent to a command-line option `--foo="Bar"'. I was just thinking about reasonable names for these options.
Frank: you could just do an include file with all the path options, and you just change this file... That's how I do almost every thing (compiler options and defines in a separate "config file" which I include everywhere).
Pierre Phaneuf
"The use of COBOL cripples the mind; its teaching should, therefore, be regarded as a criminal offense." - Edsger W. Dijkstra.