🚀 go-pugleaf

System: Franz lisp v39 on a Sun II w/ v2. of Sun's OS (BSD 4.2)

I have been running into some strange behavior when using the "printres" 
option in trace, where the trace is set in the program.  Unfortunately, I
haven't been able to isolate it in a small testcase.  But maybe an example
of the problem will help.  Consider the following code embedded inside another 
(intrepreted) function:
	(trace (foo printres some-print-func))
	:
	:
	(untrace)
("foo" is compiled, if that matters.)
The call to "untrace" does not turn off the trace on "foo" when called from 
within the other function, although trace can be turned off from the top level. 
But even then, if you set a trace on foo again, it doesn't work right, e.g. if 
you say (trace foo), trace resumes using "some-print-func" rather than doing a 
simple trace.  There appears to be some tracing info on the plist of "foo", but 
setting this to nil doesn't help...

Has anyone else run into this problem, and if so, have you been able to isolate
a small testcase?  Better yet, have you come up with a solution?
-- 
Mike Maxwell
Boeing Artificial Intelligence Center
	...uw-beaver!uw-june!bcsaic!michaelm