Hi Andreas, > The on error concept surely isn't the most elegant one but > it already exists and Basic programmers are used to it. So > if it can be extended moderately to support UNO exception > handling I would prefer it to introducing another complete- > ly different concept. I think as we all are very C++ and/or > Java oriented we always risk to regard the C++/Java langua- > ge element as the "right" ones. IMHO in a language binding > UNO concepts should be adopted as near to the target lan- > guage as possible because the users of this language should > use it in the first place.
Convinced. > VB(A) has a command "raise" that currently is not supported > in OOo Basic but it does something similar. So also for > throw there could be a native Basic variant. And why do we > need a try/catch together with a throw/raise as long as we > have a similar functionality in on error? Okay, didn't know about "raise". I'd now vote for implementing the "CurrentUnoException", plus "raise", where the latter is able to raise an UNO exception. That would fit to the language, and make Basic fully UNO-exception-aware. Ciao Frank -- - Frank Schönheit, Software Engineer [EMAIL PROTECTED] - - Sun Microsystems http://www.sun.com/staroffice - - OpenOffice.org Base http://dba.openoffice.org - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
