Hi Randy,
This is a good idea, as I've already met such situation
in real life, and it's really annoying to see the
screen just "vanish" with no trace.
Maybe the general answer to this, is that we may
redirect all internal errors to a file, because
internal errors are currently inherently lost in
most full screen apps. (Recursive errors are
generating internal errors already IIRC).
Brgds,
Viktor
On 2008.07.02., at 17:21, Randy Portnoff wrote:
Hi all,
Similar to the way Harbour now traps GPF's (and logs some info in a
text file), can it also detect race conditions and log that as
well? I am referring to situations where recursion occurs repeatedly
which causes the app to just exit (ie. vanish). Ideally, a runtime
error would be best.
For example, this causes the app to vanish.
func main()
SomeFunc()
return nil
func SomeFunc()
Main()
return nil
Regards,
Randy.
_______________________________________________
Harbour mailing list
Harbour@harbour-project.org
http://lists.harbour-project.org/mailman/listinfo/harbour
_______________________________________________
Harbour mailing list
Harbour@harbour-project.org
http://lists.harbour-project.org/mailman/listinfo/harbour
