From: root <da...@ax...> - 2006-01-26 00:57:49
|
i might add a second vote to not expecting -- as the first argument of an executable file. i'm using this standalone feature to allow me to replace a C++ program and this will be an issue as soon as i push out the resulting change. it does make a "drop-in replacement" harder and is a non-standard way of handling command line arguments. i suppose 'scripting' uses of executables was a prior use and i can see why it works the way it does. however it is easier for someone to handle the extra initial arg if they plan to use it in a script than be forced to supply an arg you can't override. Tim Daly |