Menu
▾
▴
[Oorexx-rfes] [ oorexx-Feature Requests-1460633 ] Add condition('o') for UNKNOWN methods ...
|
From: SourceForge.net <no...@so...> - 2007-10-03 12:55:53
|
Feature Requests item #1460633, was opened at 2006-03-29 07:22 Message generated for change (Comment added) made by bigrixx You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=684733&aid=1460633&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: None Group: Rejected >Status: Pending Resolution: Rejected Priority: 5 Private: No Submitted By: Rony G. Flatscher (orexx) Assigned to: Nobody/Anonymous (nobody) Summary: Add condition('o') for UNKNOWN methods ... Initial Comment: Hi there, whenever an UNKNOWN method is invoked because an object could not find a method by the same name as the received message and there is an UNKNOWN method defined in the searched classes, that gets invoked by the runtime, supplying the method name and an array object containing the supplied arguments, if any. In this situation - like in a SIGNAL handler - it may become important to get at the information in which program in which statement this exception has occurred. Such information is usually made available via the CONDITION()-BIF, where CONDITION('o') will return a directory object containing relevant information. In the case of an UNKNOWN method at the moment no condition-object can be received if issuing the CONDITION('o') BIF. Such information would be very valuable in debugging/logging situations, comparable to what one might be interested in while in exception handlers (eg. "CALL/SIGNAL ON ANY"). Alternatively, maybe a generic INSPECT()-function which would carry information like tracebacks, exception information, values of RESULT, RC, SIGL, ("self", "super", if issued from within a method) at the time of the call might even proof more helpful. ---------------------------------------------------------------------- Comment By: Rick McGuire (bigrixx) Date: 2007-10-03 08:55 Message: Logged In: YES user_id=1125291 Originator: NO Notice: This RFE is slated to be rejected. Reason: See the RFE item in the SourceForge Tracker system for the rejection reason. To appeal this rejection please contact the Appeals Committee via Mr. Chip Davis oor...@oo... All further correspondence on this RFE should be directed to the Appeals Committee and MUST include this RFE number. The decision of the Appeals Committee is final. ---------------------------------------------------------------------- Comment By: Rick McGuire (bigrixx) Date: 2007-10-03 08:55 Message: Logged In: YES user_id=1125291 Originator: NO Gathering such information for conditions is an extremely heavyweight operation, and should be confined to actual exception conditions, not actual mainstream mechanisms such as UNKNOWN. Adding this would have significant performance impacts on directorys, oleobject, monitors, etc., which all rely on efficient operation of the UNKNOWN method to function. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=684733&aid=1460633&group_id=119701 |