|
From: SourceForge.net <no...@so...> - 2006-07-19 03:52:30
|
Bugs item #859899, was opened at 2003-12-14 10:47 Message generated for change (Comment added) made by robert_dodier You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=104933&aid=859899&group_id=4933 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: Lisp Core Group: None >Status: Closed >Resolution: Fixed Priority: 5 Submitted By: Robert Dodier (robert_dodier) Assigned to: Nobody/Anonymous (nobody) Summary: TIMER and TRACE mutually exclusive Initial Comment: TIMER(FOO) has no effect if TRACE(FOO) is already in effect. -- if you call UNTRACE(FOO) and then TIMER(FOO) it works as expected. TIMER(FOO) after TRACE(FOO) yields "FOO is already traced" and timing numbers are not collected for FOO. Likewise TRACE(FOO) has no effect if TIMER(FOO) is already in effect -- if you call UNTIMER(FOO) and then TRACE(FOO) it works as expected. UNTIMER(FOO) turns off TRACE(FOO) and UNTRACE(FOO) turns off TIMER(FOO). In mtrace.lisp, $TIMER calls MACSYMA-TIMER, which calls MACSYMA-TRACE-SUB. From reading the code, I can see where the "FOO is already traced" message comes from, but I don't see why TIMER fails to go into effect in that case. There's nothing in the available documentation that suggests TIMER and TRACE are mutually exclusive. ---------------------------------------------------------------------- >Comment By: Robert Dodier (robert_dodier) Date: 2006-07-18 21:52 Message: Logged In: YES user_id=501686 Documentation for timer and trace now states that the two are mutually exclusive. That behavior seems fine; when you're tracing something, it will take longer to execute so the timer values would be inaccurate anyway. Closing this report as fixed (because the documentation was updated). ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=104933&aid=859899&group_id=4933 |