CBFalconer wrote:
Frank Heckenbach wrote:
CBFalconer wrote:
... snip ...
I am arguing that I see no point to the practice, and that stopping all consideration of the source file after the final '.' is desirable. I may well have missed some reason for allowing such practices. Maybe Borland did allow such; if so I never used it and never missed it.
Quite the contrary, actually, i.e. in this case you're on the same side as Borland (and I disagree with you and them ;-).
I guess the millenium HAS arrived!!! :-)
;-)
BTW, although such may already exist and I have missed it, it would be handy to have an environment variable to preset default command line options for a gpc installation. This would require another option to ignore that, such as --no-cmdline-defaults, to ignore whatever is in, say "$gpc-cmdline-defaults" :-) An alternative would be the switch "--use-cmdline-defaults" which would avoid any conflicts with existing scripts, etc.
The latter is the reason why it should not be the default (I think this was discussed recently).
Your `--use-cmdline-defaults' would not suffer from this problem, but OTOH, this doesn't seem to make things easier than passing the variable explicitly, i.e.:
gpc --use-cmdline-defaults foo.pas
vs.:
gpc $gpc-cmdline-defaults foo.pas
(or whatever the shell syntax is -- I think it's %...% in command.com). Besides, the latter is more flexible, since you can have any number of variables set (typically I have one for debugging (additional checks) and one for release (optimizations) purposes) and use them at will.
Frank