Re: [Lilypond-auto] Issue 4213 in lilypond: Patch: Context: prevent dangling references in child contexts when the daddy is destroyed

[lilypond]

Comment #6 on issue 4213 by address@hidden: Patch: Context: prevent dangling  
references in child contexts when the daddy is destroyed
https://code.google.com/p/lilypond/issues/detail?id=4213

> Updates:
>         Labels: -Patch-review Patch-needs_work

> Comment #5 on issue 4213 by
> address@hidden: Patch: Context:
> prevent dangling references in child contexts when the daddy is
> destroyed
> https://code.google.com/p/lilypond/issues/detail?id=4213

> > Markups are expanded when contexts already finished iteration.
> > Context properties don't actually carry meaning by that time.

> How about failing with an error message if any contexts survive after
> iteration?

Well, some context may finish iteration and still be kept alive by being
in another context's associated-context variable (for example).

And destruction may be delayed arbitrarily because of conservative
garbage collection.  But contexts should likely detach from the context
hierarchy once their iteration completes.  Once it does that, a child
context will no longer be able to get/update its context properties.
But normally, child contexts will be detached first.

> > Any "proper" termination of a context should already disconnect it
> > from its parents (and/or detach the children?).

> I will investigate the circumstances in which ~Context() is called
> when there are still children.  That is a good reason for a
> programming_error message, right?

More like a failed assertion.


--
You received this message because this project is configured to send all  
issue notifications to this address.
You may adjust your notification preferences at:
https://code.google.com/hosting/settings