Frank Schönheit - Sun Microsystems Germany schrieb:
Hi Daniel,
What happens if UNO_QUERY_THROW is used instead?
...
What is the reason you have introduced UNO_SET_THROW?
It spares the queryInterface call. For a pattern like
Reference< XFoo > xFoo = xBar->getSomeFoo();
// ensure that xFoo is not NULL, which would be a violation
// of xBar's constraint
...
it just felt wrong (since potentially too expensive) to do
Reference< XFoo > xFoo( xBar->getSomeFoo(), UNO_QUERY_THROW );
UNO_SET_THROW is cheaper in this case.
Ok, understood. Thanks.
Daniel
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscr...@api.openoffice.org
For additional commands, e-mail: dev-h...@api.openoffice.org
