[Gambas-user] Error.Backtrace

[Benoît Minisini]

Le 17/01/2014 02:33, Ian Haywood a écrit :
> On 17/01/14 10:11, Benoît Minisini wrote:
>> Le 16/01/2014 23:12, Ian Haywood a écrit :
>
>> For a TRY that does not call functions, it is not computed, so you get
>> the previous stack backtrace.
> not computing it is OK (as the combination of Error.Text and Error.Where
> gives
> us all the information anyway). The problem is leaving old data in
> there, there is no way to detect this is bogus data and leads to many
> hours trying to debug the wrong bit of code (our project has 200k SLOC
> so we need to know where to look!)
> Surely it wouldn't slow performance to set Error.Backtrace to NULL?
>
>> I admit it is actually a bit weird, but I don't understand why it is a
>> problem. You should use TRY when you really don't care with the error.
> Hmm, because Catch only operates at the level of a whole function we do use
> TRY and test for errors a fair bit.
>
> Ian
>

Done in revision #6090: when the stack backtrace is not computed, the 
Error.Backtrace property is now always set to NULL.

Regards,

-- 
Benoît Minisini