Hi Stephan,
>>A complex return type? A complex type as output parameter, with a
>>boolean return type?
>
> Out-parameters are frowned upon in UNO circles (because they have
> awkward to use mappings in languages like Java), so the best solution
> seems a complex return type---com.sun.star.beans.Optional might be handy
> here.
So you suggest to use awkward-to-use output parameters with
awkward-to-use complex return types?
(
while ( listenerIter.hasMore() )
{
retVal = ((listener*)iter.next())->approve();
if ( !retVal.veto )
continue;
handleVeto( retVal.vetoDetails, retVal.vetoInstance );
}
?)
Hmm. None of those options sounds convenient to use to me, but be it.
What about
struct ApprovalOrVeto_OrAnyBetterName
{
boolean IsVeto;
string Veto;
any Reason;
XInterface Context;
};
?
Thanks & 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]
