On 15/09/06, Axel Liljencrantz <[EMAIL PROTECTED]> wrote: > On 9/14/06, Beni Cherniavsky <[EMAIL PROTECTED]> wrote: > > But things like ``end (echo no)`` are useless, because the right > > answer is always known and you only wish to state it clearly. If you > > disallow expansions in end's argument, it could be checked as part of > > the syntax checks before the command is ever run, which I think would > > be much more intuitive. > > You could do that, but there is honestly no reason to _ever_ write > 'end (echo no)', so I don't see why you should change the language > syntax to make it larger and less consistent just to disallow it. > To allow the error to be detected at parse time, rather than after some (perhaps wrong) commands were executed. The whole point of the ``end foo`` feature was to detect brocken syntax; if it isn't detected early enough, the feature is half-useless.
Disabling expansions is not a goal in itself, it's just needed (as far as I understand) so it can be checked at parse time. I don't know whether this special-casing can be easily implemented. It might not be worth it. -- Beni Cherniavsky <[EMAIL PROTECTED]>, who can only read email on weekends. ------------------------------------------------------------------------- Using Tomcat but need to do more? Need to support web services, security? Get stuff done quickly with pre-integrated technology to make your job easier Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo http://sel.as-us.falkag.net/sel?cmd=lnk&kid=120709&bid=263057&dat=121642 _______________________________________________ Fish-users mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/fish-users
