[Harbour] Re: Incorrect call stack at error, and recursive error

2008-05-07 Thread Miguel Angel Marchuet
Przemyslaw Czerpak escribió: On Wed, 07 May 2008, Miguel Angel Marchuet wrote: It's correct. In hb_stackDispCall() (this function is used only by internal error handler) we show only pure function names without information about codeblocks source. If it's a problem then I can change it to presen

[Harbour] Re: Incorrect call stack at error, and recursive error

2008-05-07 Thread Przemyslaw Czerpak
On Wed, 07 May 2008, Miguel Angel Marchuet wrote: > >It's correct. In hb_stackDispCall() (this function is used only by > >internal error handler) we show only pure function names without > >information about codeblocks source. If it's a problem then I can > >change it to present call stack just li

[Harbour] Re: Incorrect call stack at error, and recursive error

2008-05-07 Thread Miguel Angel Marchuet
It's correct. In hb_stackDispCall() (this function is used only by internal error handler) we show only pure function names without information about codeblocks source. If it's a problem then I can change it to present call stack just like in hb_vmRequestCancel(). Shows EVAL instead of ERRORDIAL

[Harbour] Re: Incorrect call stack at error, and recursive error

2008-05-07 Thread Przemyslaw Czerpak
On Wed, 07 May 2008, Miguel Angel Marchuet wrote: > With this example we can see how call stack inform incorrect function > at harbour... It's correct. In hb_stackDispCall() (this function is used only by internal error handler) we show only pure function names without information about codeblocks