I don't like the idea of having a hundred numbered errors and a hundred more errors with the same number. If you're going to add even one unnumbered message (or two messages with the same number) then ditch the error numbers altogether.
Make sure the support for translating error messages is no worse than it is under the current system -- right now, AXIS can display the interpreter error messages translated into the user's language if a message catalog has been prepared. Since we have stuff like a "call stack" now, have a way to provide that call stack to the user of the library, so that I can tell which call to 'o999 sub' caused the problem. Inspecting variable values should be possible too. You've created a programming language, it's time to write the source-level debugger, or at least the hooks that make one possible. Provide a way for the program to specify its own error messages. If 'o999 sub' required that one argument be an angle between -180 and 180, let it show that to the user and end parsing. (in this case, the requirement that the message be automatically translatable is waived) Jeff ------------------------------------------------------------------------- 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 _______________________________________________ Emc-developers mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/emc-developers
