On Sat, 26 Apr 1997 13:20:36 -0400 Jack De Winter
<jack(_at_)wildbear(_dot_)on(_dot_)ca>
wrote:
6. Errors in Processing a Script
The stipulation that implementations SHOULD NOT try to recover from a
script with errors is a problem for me. Aborting within an 'if' clause
makes sense to me, but to totally stop filtering if any error is encountered
is the wrong thing to do. I would venture a guess that most users would
consider this a very bad characteristic of the mechanism.
Personally, I would like to see an 'onerror' command that would allow you
to try and trap an error. This was actually a nice feature on one of
the basics I used in grade school many years ago, as there were some cases
where it came in useful.
Sounds like a good idea.
I would like to see an optimization made to the grammar. In the elements
of an if-clause condition that use a list as an argument, I would like to
see the ability to not necessarily have the parens for single-item lists.
It might also be nice for users to not have to use quotes around words that
don't need them.
I agree on the single item lists, but not on the quotes. The UA can
put them in, and it makes parsing a lot simpler.
Exactly.
Wow - Jack and I agree on TWO things at once. A truly auspicious day.
Makes me nervous like when I write 500 lines of code and get no syntax
errors on the first compile :-).
Cheers.
---
Steve Hole VP, Research and Development
The Esys Corporation EMail: steve(_at_)esys(_dot_)ca
900 10040 - 104 St. Phone: 403-424-4922
Edmonton, AB, Canada Fax: 403-424-4925
T5J 0Z6