Hi Frank,
> Hmm. What's the advantage of this over using
> ::rtl::Reference< MyUnoImpl > ptr( new MyUnoImpl );
> xUno->callingUno( uno::Reference( ptr.get() ) );
> takeNonUnoPtr( ptr );
There is no advantage over the example you gave.
But it eases the implementation if you _already have_ a
Christian Lippka wrote:
> And if there is still someone who thinks the office should crash if a
> component does not fullfill its contract, please drop me a mail.
???
I think no one ever stated this being sensible in this thread.
-Daniel
--
Thorsten Behrens wrote:
> this was about
>
> Reference x(y->baz());
> assureNotNull(x);
>
> vs.
>
> Reference x(y->baz(),
>UNO_QUERY_SPECIAL_MAGIC);
IMO especially vs. Frank's suggested
Reference x(y->baz(),
UNO_SET_THROW);
> I was saying that thi
Hi Kay,
so what ctors did you actually add to the existing?
-Daniel
[EMAIL PROTECTED] wrote:
>
> Type: info
> Title: Convenience c'tors for uno::Mapping&uno::Environment
> Posted by: [EMAIL PROTECTED]
> Affected: People directly dealing with the C++ Uno Runtime cla
