From: SourceForge.net <no...@so...> - 2009-07-13 20:59:55
|
Bugs item #2820937, was opened at 2009-07-13 16:06 Message generated for change (Comment added) made by bigrixx You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=684730&aid=2820937&group_id=119701 Please note that this message will contain a full copy of the comment thread, including the initial issue submission, for this request, not just the latest update. >Category: Interpreter Group: None >Status: Closed >Resolution: Invalid Priority: 5 Private: No Submitted By: Mark Gaubatz (mgaubatz) >Assigned to: Rick McGuire (bigrixx) Summary: Traceback incorrect Initial Comment: With and without signal on syntax and raise propagate in 4.0 RC 1, traceback starts with use strict instruction (or raise instruction if using raise). Expected is that traceback starts at the line number indicated by the syntax error message. call foo call bar ::routine foo signal on syntax use strict arg fn return syntax: raise propagate ::routine bar use strict fn return Example results from call to foo: 111 *-* use strict arg fn 36 *-* rc = foo(/*fn*/) 25 *-* return .program~new~make("foo") REX0040E: Error 40 running /home/mark/foo.rex line 36: Incorrect call to routine REX0374E: Error 40.3: Not enough arguments in invocation of FOO; minimum expected is 1 Example results from call to bar: 111 *-* use strict arg fn 36 *-* rc = bar(/*fn*/) 25 *-* return .program~new~make("bar") REX0040E: Error 40 running /home/mark/bar.rex line 111: Incorrect call to routine REX0374E: Error 40.3: Not enough arguments in invocation of BAR; minimum expected is 1 ---------------------------------------------------------------------- >Comment By: Rick McGuire (bigrixx) Date: 2009-07-13 16:59 Message: This is working exactly the way it was intended. The raise propagate raises a new condition at the point of the caller, so the line number is reported correctly. The traceback information from the earlier levels is maintained because you've asked for this to be propagated. ---------------------------------------------------------------------- Comment By: TheDavidFactor (darthapache) Date: 2009-07-13 16:34 Message: While I find this issue some what confusing as well, this should be an RFE not a Bug because this behavior is consistent with ooRexx 3.2 (and I assume older versions as well) ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=684730&aid=2820937&group_id=119701 |