> It seems to me that currently the include inset needs to know about
> its parent to work correctly. To make this change, we'd have to pass
> extra information in some cases.

Yes, this is needed, but this is a different situation:

We are talking about two different kinds of ownership:

1. Which Buffer does an inset belong to?

2. Which Buffer does this included Buffer belong to?

I'm talking about eliminating the explicit management of
type 1 ownerships:  Insets do not need to know who owns them.

Type 2 ownership is different:  I agree that IncludeInsets
needs to hold a Buffer-pointer, but this is not such a big
problem, because it's not often that an Included document
changes owner (if ever.)

Greets,

Asger

Reply via email to