ref-count assertion in cppu::OWeakObject ...
noel at peralex.com
Mon Aug 6 05:05:51 PDT 2012
On 2012-08-06 13:53, Michael Meeks wrote:
> Anyhow - the suggestion is, assuming we can find/cleanup this sort of
> badness [ incidentally a GObject takes a reference on itself during it's
> destruction to avoid double destruction ], is it a good idea to have an
> abort/assert whatever is fashionable in run-time code so we can be
> confident that we have caught these cases earlier ? I for one prefer an
> assertion-fail abort-app to a hard-to-catch memory corrupter later.
My motto : "Fail early, fail hard"
Causes some screaming early on, then later on, generates a pleasant
quietness from the people using my software :-)
More information about the LibreOffice