Hi Frank,
> Hi Daniel,
>
>>> may I ask where those leaks are reported?
>> Those leaks are OSL_asserted.
>
> When? Upon app shutdown? What if parts of the infrastructure for OSL
> assertions is not in place then anymore?
Yes, upon process shutdown. There is an extra checkObjectCount()
function that can be used during the process lifetime.
I assume sal is still in place and functional until your code has shut
down; you linked against it.
>> Just for completeness: You can also take a pro-build and recompile some
>> code with OSL_DEBUG_LEVEL > 0 (e.g. debug=t).
>
> Is this compatible? That is, consider a header file containing
> class Foo : public DebugBase< Foo >
> {
> // ...
> };
>
> Now if the implementation file is compiled without debug, but a certain
> client file of the header is compiled with debug=1 (resulting in
> OSL_DEBUG_LEVEL > 0), will this client file crash, or are the debug- and
> non-debug "versions" of DebugBase binary compatible?
DebugBase is an empty class in both cases, I expect this to work (never
tested!). But I would avoid such scenarios, because it violates the One
Defintion Rule (ODR). Nobody can garantee this works on all compilers.
> Sorry for being that inquisitive :)
BTW: We've had discussion about this last year:
<http://www.openoffice.org/servlets/ReadMsg?list=dev&msgNo=15366>
DebugBase has been the outcome.
regards,
-Daniel
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
