Hi,
>> What about
>>
>> struct ApprovalOrVeto_OrAnyBetterName
>> {
>> boolean IsVeto;
>> string Veto;
>> any Reason;
>> XInterface Context;
>> };
>
> That struct would have to be created, though with empty members, even in
> the all-good-no-veto case. Depending on the scenario this may cause
> significant unnecessary overhead with mass objects. Shouldn't we better
> have a simple boolean return instead and explicitly act on a veto?
What about an UNO interface that returns an empty reference if there is
no problem?
I used this for the spell checking in XSpellAlternatives.
I thought the overhead for calling the functions of that interface small
compared to always returning a struct. This of course presumes that
spelling errors are not that common in regular written text.
Thomas
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
