Hi,
hadn't time in the last weeks to fix this. I will do this in the next
days/weeks.
Thomas
On 03/21/2011 08:07 AM, David Tardon wrote:
> On Fri, Mar 18, 2011 at 08:53:36PM +0100, Thomas Arnhold wrote:
>> Hi,
>>
>> some days ago I converted all DBG_ERROR[1-9], which had a printf like
>> format
On Fri, Mar 18, 2011 at 08:53:36PM +0100, Thomas Arnhold wrote:
> Hi,
>
> some days ago I converted all DBG_ERROR[1-9], which had a printf like
> format string, to OSL_TRACE. David Tardon pointed me out that this
> slightly changed the behavior, because the according OSL variant of
> DBG_ERROR is
Thomas Arnhold wrote:
> Has anyone objections about this new behavior?
>
I guess having the old behaviour (i.e. abort or msgbox) restored
would be good - though clearly the whole assertion concept (and how
we handle their occurence) needs a lot of love ...
Cheers,
-- Thorsten
pgpo173LHiwTb.pgp
Hi,
some days ago I converted all DBG_ERROR[1-9], which had a printf like
format string, to OSL_TRACE. David Tardon pointed me out that this
slightly changed the behavior, because the according OSL variant of
DBG_ERROR is OSL_FAIL (which is _OSL_ENSURE), which therefore breaks the
debug if OSL_FAI
