Hi Frank,
Let's start with the testtool. The testtool Basic is not similar
to OOo Basic, it *is* OOo Basic, extended by some testtool speci-
fic commands and some convenience functionality. The try/catch
belongs to the latter. According to Gregor it's only another syn-
tax for the on error functionality that is supported by Basic any-
way. On error also supports UNO exceptions but in a very limited
way. Every UNO exception is mapped to the Basic Runtime Error 1.
hey, so we get try/catch for free ;)
At least a beginner's version... :-)
Maybe the problem is solved in the mean time, but at least when
I addressed this problem the first time, there was no way to
get the real (UNO) exception type from e. If there is a way now,
e.g. by using C++ RTTI, the implementation of a better exception
support in OOo Basic really shouldn't be too difficult.
::cppu::getCaughtException could be used. It returns an Any, which
contains the full exception which has just been caught. Quite
convenient, I use it all the time since I know about it ...
Great, this would solve the problem. Maybe we then should
think about a cheap solution, at least for now. E.g. a spe-
cial object named CurrentUnoException or something like
that could be provided by Basic in case an UNO exception
error occurs containing the Exception object. This would
match with the err variable concept and we wouldn't have
to implement the complete try/catch syntax that isn't
Basic like anyway.
Regards
Andreas
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
