Re: [Libreoffice-commits] update string copy semantics to be undefined in a non-crashing way

On Thu, Oct 4, 2012 at 7:48 AM, Michael Meeks <michael.meeks@suse.com> wrote:
>         The arguably bit was near the crux of the discussion - IIRC it was
> decided that aborting was not a great idea

I believe the only debate was whether aborting in release code was a
desirable feature...
But surely there is no arguement that an assert() should abort in debug code.

and in this case, the whole endeavour was not to remove the assert
(i.e abort() ) in debug code, but rather to avoid memory overflow bug
in release code, by sanitizing the consequence of a mis-use of the API
that make it to release code...

Norbert