From: Rony G. F. <Ron...@wu...> - 2012-07-11 14:46:40
|
On 11.07.2012 16:43, Rick McGuire wrote: > Already something in the works in the trunk version. The condition > object will contain a set of stack frame objects that will go all the > way to the original source of the error. A stack frame will contain > the method or routine for that particular level, so you can determine > everything you need to know about the error. Great, thank you very much! ---rony On Wed, Jul 11, 2012 at 10:37 AM, Rony G. Flatscher <Ron...@wu...> wrote: >> Just noted the comment and resolution of >> <https://sourceforge.net/tracker/?func=detail&atid=684730&aid=3170662&group_id=119701>. As it is not >> possible to use the comment field anymore, I am turning to the developer list. >> >> The reported observation, that the entry "program" in the error directory, is changed to the program >> in which the condition is intercepted after doing a "raise propagate" means, that in those programs >> it is not possible to determine in which program the condition got originallly raised. All other >> condition-related information like "errortext", "code", "message" etc. seem to remain unchanged. >> >> Is there another way to determine in which program originally a condition got raised, if >> intercepting raised conditions in different programs? >> >> If not, would it make sense to open an RFE to ask for a new entry in the error directory supplied by >> condition('o') which contains and keeps the program name where originally the condition got raised? >> >> ---rony >> |