Hi Mathias, >> However a reasonable error handling would look like, IMO carefully >> re-designing UNO to add more exceptions specifications to (a lot of) >> methods is a must-have. > > +1 > > Just to play the devil's advocate: without careful considerations that > would end in adding "throws css.uno.Exception" to any method, though > perhaps it's the right approach for all generic APIs (generic APIs need > generic exceptions - don't they?).
Don't think so. I suppose the line is to be drawn (if at all) between ¨high level¨ and ¨low level¨ API (whatever that means :), where the former has an increased chance of throwing a WrappedTargetException (which I'd consider more appropriate than a generic Exception). > OTOH designing exceptions right is very hard and often needs a lot of > thinking. So I don't expect that we can fix that in a "big bang" > release, we will need quite some time to fix that. I would be happy if we would allow for such fixing. I don't want to fix all of those at the same time, but being able to fix them incrementally, as they bite me, would be great. Ciao Frank -- - Frank Schönheit, Software Engineer frank.schoenh...@sun.com - - Sun Microsystems http://www.sun.com/staroffice - - OpenOffice.org Base http://dba.openoffice.org - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - --------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscr...@openoffice.org For additional commands, e-mail: dev-h...@openoffice.org
