Hi Stephan, > I'm not sure I understand your last sentence. "UNO_QUERY_THROW" does > more than "set/if.is()" (namely, doing a queryInterface call), and this > extra activity is inconvenient for you? In how far is it inconvenient?
Wrong wording, perhaps. It's not inconvenient in the sense of "cumbersome to use", but in the sense of "I don't feel comfortable with it". The UNO_QUERY_THROW pattern does an - unnecessary - queryInterface, and I am not sure if this will yield problems in the future. It currently probably doesn't, but who knows how the implementation of the component will look in the future, or in which context my current implementation will be used? I would simply feel more relaxed with not having this additional queryInterface. Ciao Frank -- - Frank Schönheit, Software Engineer [EMAIL PROTECTED] - - Sun Microsystems http://www.sun.com/staroffice - - OpenOffice.org Database http://dba.openoffice.org - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
