Re: I need to better understand our css::uno::Reference

Stephan Bergmann <sbergman -AT- redhat.com>
Wed, 18 Jun 2014 17:04:02 +0200

On 06/18/2014 04:21 PM, Lionel Elie Mamane wrote:

Why does the attached patch lead to a segfault in "make
JunitTest_dbaccess_unoapi"? (The patch is against very recent master,
as in "I pushed right before hitting send on this email".)

Essentially, it changes, in code internal to a class,
Reference< XResultSet >
by
Reference< OResultSet >

Short answer (from just browsing the top of FOO.patch): Usecss::uno::Reference<X> only for (C++ classes representing) UNOinterfaces, and use rtl::Reference<C> for C++ classes implementing UNOobjects.


Stephan

Context

I need to better understand our css::uno::Reference · Lionel Elie Mamane
- Re: I need to better understand our css::uno::Reference · Stephan Bergmann
  - Re: I need to better understand our css::uno::Reference · Lionel Elie Mamane
    - Re: I need to better understand our css::uno::Reference · Stephan Bergmann
      - Re: I need to better understand our css::uno::Reference · julien2412
        
        Re: I need to better understand our css::uno::Reference · Stephan Bergmann
      - Re: I need to better understand our css::uno::Reference · Lionel Elie Mamane
        
        Re: I need to better understand our css::uno::Reference · Stephan Bergmann

Privacy Policy | Impressum (Legal Info) | Copyright information: Unless otherwise specified, all text and images on this website are licensed under the Creative Commons Attribution-Share Alike 3.0 License. This does not include the source code of LibreOffice, which is licensed under the Mozilla Public License (MPLv2). "LibreOffice" and "The Document Foundation" are registered trademarks of their corresponding registered owners or are in actual use as trademarks in one or more countries. Their respective logos and icons are also subject to international copyright laws. Use thereof is explained in our trademark policy.