Daniel Beck wrote:
I created a ContextMenuInterceptorClass, that registers once, then
starting openoffice, to the current frame.
But then, it doesn't work then I opens a new frame, because I is
registered, from the beginning on, at the first active StarOffice component.
So ... Either
Hello Malte,
I like leak detection, but I think inheritance is not so useful here,
because you can't simply add leak detection to a class 'on demand',
without compiling all following modules.
There is no need to recompile derived classes/modules, because the
LeakGuard-ed class references
Malte Timmermann [EMAIL PROTECTED] writes:
I like leak detection, but I think inheritance is not so useful here,
because you can't simply add leak detection to a class 'on demand',
without compiling all following modules.
We already have some leak detection in tools/debug.hxx:
DBG_CTOR and
One nit: since the automatic implementation name derivation looks kind
of fragile (and most of the time, I _do_ declare my service
implementations in anonymous namespaces) - how about disabling that
feature by default? I have the impression that not much of OOo
development outside Sun takes
Malte Timmermann wrote:
Just in case someone want to fix it, here some background:
- FontSizeBox show fonts in Points
- Writer remembers font size in Twips
- Calc/Impress remember font sizes in 100th mm
If only things were that simple. Calc cell attributes use twips
internally, only formatted
Hi Daniel,
I'd like to present/discuss a recent helper, called rtl::LeakGuard which
helps to find leaking free store objects.
To cite Thorsten: Great stuff!
In non-pro builds, the LeakGuard OSL_ASSERTs any undestroyed (leaking)
objects while in product builds the LeakGuard class is just
Hello
My name is Suleiman, I am doing master of information technology
(Professional) at the University of Southern Queensland USQ in
Australia, I need to do a project course, and I was thinking about doing
some work on some of the open source applications, when I was looking
online and searching,
Hi Daniel,
I'd like to present/discuss a recent helper I have developed which IMO
simplifies the implementation of UNO services in C++ a lot.
Using the following (what I call) service declaration, the developer can
concentrate on implementing her service's interfaces, e.g.
again, you managed
Hello Niklas,
namespace sdecl = comphelper::service_decl;
sdecl::ServiceDecl const myDecl(
sdecl::class_MyImpl(),
org.openoffice.MyService,
[optional my.implementation.name] );
If used as a global object, with a constructor that is executed when the
DLL is loaded, that won't
We should talk about the LeakGuard when consolidating the debug macros,
as Frank suggested.
Please don't introduce before.
I also suggest to have a macro for it, which simply expands to nothing
in product builds.
If we do anything in this direction, I think it shouldn't be only leak
detection,
Hi Daniel,
Well, at least the last point of the statistics (the only one I ever
used: the number of leaked objects) serves exactly this purpose. It
would, for instance, enabled QA to regularily do leak tests on certain
usage scenarios.
LeakGuard OSL_ASSERTs if the object count is non-zero upon
Hi Malte,
We should talk about the LeakGuard when consolidating the debug macros,
as Frank suggested.
Please don't introduce before.
Uh. Let's not wait for something which perhaps happens in 2007.
Introduce it when it's there, and when it's needed: now.
I also suggest to have a macro for
Hi Malte,
We should talk about the LeakGuard when consolidating the debug macros,
as Frank suggested.
Please don't introduce before.
Uh. Let's not wait for something which perhaps happens in 2007.
Introduce it when it's there, and when it's needed: now.
I also suggest to have a macro for
Hi Daniel,
IMO it doesn't matter whether you create that data (mostly the
implementation name) at the point of loading the library or slightly
later when the UNO service needs to be instantiated.
It might be everything from slightly later to never (because perhaps
sevice Foo from lib A is
Hi list-members,
There was a change in the bidirection character type of minus/hyphen
(Unicode 002D) from Unicode 4.0 to Unicode 4.0.1. It was changed from ET
(European Numeric Terminator) to ES (European Numeric Separator). I
would like to implement this in my OOo build. How do I do it?
Thorsten Behrens wrote:
Daniel Boelzle [EMAIL PROTECTED] writes:
I'd like to present/discuss a recent helper I have developed which IMO
simplifies the implementation of UNO services in C++ a lot.
[...]
So what do you think? Comments, please.
Great stuff! Always having to write so much
16 matches
Mail list logo
