Request: trace-define for non-procedures

Bug #316626 reported by Michael D. Adams
2
Affects Status Importance Assigned to Milestone
Ikarus Scheme
Fix Committed
Wishlist
Abdulaziz Ghuloum

Bug Description

Currently trace-define gives an error when defining a non-procedure:

> (trace-define foo 1)
Unhandled exception
 Condition components:
   1. &assertion
   2. &who: trace-define
   3. &message: "not a procedure"
   4. &irritants: (1)

This limits the utility of tricks like (import (rename (ikarus) (trace-define define))) or similar if there are non-procedure defines involved.

I see two possibilities (there may be others). The first is the simply have trace-define be silent on non-procedures. The second is to have trace-define trace the evaluation of the right hand side when the right hand side is a non-procedure. The later may be a mildly interesting tracing information for tracking down errors being thrown in a long chain of non-procedure defines.

Related branches

Revision history for this message
Abdulaziz Ghuloum (aghuloum) wrote :

Removed the error check in revision 1756. Thanks.

Changed in ikarus:
assignee: nobody → aghuloum
importance: Undecided → Wishlist
status: New → Fix Committed
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.