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
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
Frank Schönheit schrieb:
Hi Michael,
so i thought, what the heck is UNO_SET_THROW?
it seems to do the same thing as UNO_QUERY_THROW, except it does not
query, it only checks for NULL.
hmm, according to opengrok's mere 50 results, i'm not the only one who
never heard of it...
