Comment 3 for bug 457053

Revision history for this message
Christophe Rhodes (csr21-cantab) wrote : Re: [Bug 457053] Re: TRACE :PRINT doesn't handle multiple values

Nikodemus Siivola <email address hidden> writes:

> So, this behaviour is by design as far as I can tell. (If there are good
> use-case for handling multiple values, please file a new bug describing
> the desired functionality.)

 status confirmed
 importance wishlist
 tag trace easy
 done

I can come up with a use-case: what about using trace to view the state
of a hashtable before and after a function call: something like

  (trace foo :print-all (gethash 'key *table*))

It would be quite annoying for NIL to be printed, and then having to
worry about whether that actually means "key not present" or "key has
associated value NIL in *table*".

Christophe