Apart from being slightly inefficient to have to poll Tools.Standalone for _every_ invocation of pike, it's not robust enough. For starters, consider the case where I misspell my symlink:
ln -s pike rsig ./rsig dangerous.pike safe.pike Makefile ^ tab completion
Instead of complaining that the tool "rsig" doesn't exist, this would actually start interpreting "dangerous.pike", which is not at all what I wanted.
Secondly, think about Peters case where he has a symlink called for example "aido", which simply points to a pike suitable for running aido with. If some future release were to add a Tools.Standalone.aido, this would cause his aido invocations to do something else compeltely, despite that he hasn't changed them.
/ Marcus Comstedt (ACROSS) (Hail Ilpalazzo!)
Previous text:
2002-09-06 10:26: Subject: Re: -x
On Fri, Sep 06, 2002 at 01:25:05AM +0200, Marcus Comstedt (ACROSS) (Hail Ilpalazzo!) @ Pike (-) developers forum wrote:
Wouldn't work. What if I did a symlink 'pike7.3.53' pointing to a particular pike binary? I wouldn't want that to try to execute Tools.Standalone["pike7.3.53"].
why not? Tools.Standalone["pike7.3.53"] is unlikely to exist, the default should be to simply run pike as is if nothing is found in Tools.Standalone.
besides, this could be an interresting way to invoke compatibility mode.
greetings, martin.
/ Brevbäraren