Rick McGuire wrote:
> This is the correct result.  The traceback only includes lines back to
> the point where the condition was trapped.  Since your internal
> routine call inherits the signal on settings from the call, the error
> trap is triggered while still in the internal routine, so line 2 does
> not get added to the traceback.
>   
>From native code the only piece of information that is available about
conditions is the condition object retrieved by GetCondition(). If it is
not possible to get at the line number where the signal occurred [and
preferably the sourceline(sigl)], then the condition object is in some
use cases unfortunately of no great help

It seems that what is currently missing from the condition object then,
is the value of SIGL and preferably the sourceline(SIGL). Shall I open a
RFE to ask for them, or do you regard that to be useless?

---rony


------------------------------------------------------------------------------
The NEW KODAK i700 Series Scanners deliver under ANY circumstances! Your
production scanning environment may not be a perfect world - but thanks to
Kodak, there's a perfect scanner to get the job done! With the NEW KODAK i700
Series Scanner you'll get full speed at 300 dpi even with all image 
processing features enabled. http://p.sf.net/sfu/kodak-com
_______________________________________________
Oorexx-devel mailing list
Oorexx-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/oorexx-devel

Reply via email to