Re: Blueberry is not "closed" (was: Closing Blueberry)

[Rick Jelliffe <ricko@allette.com.au>]

 From: "Elliotte Rusty Harold" <elharo@metalab.unc.edu>

> That would be a naive approach. DOM could easily be implemented so this
was not an issue. For example, give every element, attribute, and processing
instruction a boolean usesBlueberry flag. Then have the document keep a
reference count of the number of Blueberry items in the document that could
be incremented and decremented as nodes were added to the document.

"Could be" does not equal "will be".  The developer will still need to check
out whether the DOM is blueberry-capable.

And, in any case, the DOM might be implemented as an access layer on an
existing database, which does not have such a flag. In such cases, the naive
approach is the only one practical.

In any case, the cost of having flags (or a collective count) updated during
every write may be greater than that of doing two passes, surely. It depends
on the access patterns.

Cheers
Rick Jelliffe