On Jul 4, 2:23 pm, "Ville M. Vainio" <[email protected]> wrote:
> On Sat, Jul 4, 2009 at 10:00 PM, Edward K. Ream <[email protected]> wrote:
> We can also maintain that information outside the nodes, e.g. maintain
> a dict that maps gnx's to reference counts (or a list of parents,
> perhaps?).
>
> This table would be per-controller, and it would have valid data at
> all times. It can be used to identify cloned nodes (those have
> refcount >1, or len(parentlist) > 1.
I dislike such schemes. They are yet another form of caching.
Besides, it probably takes exactly as much work to keep the cache
up-to-date as it does to recompute info as needed.
Anyway, I think we will find that "the simplest thing that could
possibly work"
will be good enough. Certainly, that's where I shall start.
Edward
--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups
"leo-editor" group.
To post to this group, send email to [email protected]
To unsubscribe from this group, send email to
[email protected]
For more options, visit this group at
http://groups.google.com/group/leo-editor?hl=en
-~----------~----~----~----~------~----~------~--~---
