Re: Problem with smobs

[Neil Jerram]

"Mikael Djurfeldt" <address@hidden> writes:

> On 5/30/06, Joris van der Hoeven <address@hidden> wrote:
>> > In this case my guess is that some reference to your smob remains on
>> > the stack or in some data structure associated with printing (like the
>> > print-state) immediately after printing.  That reference will very
>> > likely pretty soon disappear after some further execution.
>>
>> [...]
>> So I still would call this an undocument side-effect of "display".
>> How much precisely is kept on the stack or in print-states?
>
> I don't remember. You'll have to look it up in the source code or wait
> for a reply from someone else.

In any case this bug is fixed now in 1.8 CVS, and in the 1.6.8
release.  Does that help you?

          Neil