From: Rudi S. <ru...@co...> - 2009-07-20 16:13:57
|
On 20.07.2009, at 17:43, Tobias C. Rittweiler wrote: > Richard M Kreuter writes: > >> IIRC, tracing anything that TRACE calls is problematic; maybe this is >> what you're seeing. > > Yes, very likely. Still it seems reasonable to me to signal an > (continuable) error in case you're trying to trace a symbol from a > locked package. Is it not? IMO, trying to trace anything in the CL package should certainly raise an error - it's not only explicitly forbidden but is also likely to corrupt the user's session. (Similar to how you can't assign a non- pathname to *default-pathname-defaults* any more.) But I don't see as clear an argument for forbidding to trace functions from locked packages - I might not want to change a library, but I'd still like to trace something in order to understand how it works. Cheers, Rudi |