Confirmed users
146
edits
DOM/ContentIterator Issues: Difference between revisions
→Special-case handling of null mCommonParent values
(Content Iterator Issues) |
|||
| Line 35: | Line 35: | ||
=== Special-case handling of null mCommonParent values === | === Special-case handling of null mCommonParent values === | ||
We know the node types which are likely to give us trouble. For instance, we could create a mCommonDocument value to hold a reference to a document, if that were the common ancestor. This may lead to memory bloat, however (mCommonDocument, mCommonAttribute, mCommonEntityRef, mCommonDocumentFragment, and who knows what else we'll need pointers for, most of which will be null). | We know the node types which are likely to give us trouble. For instance, we could create a mCommonDocument value to hold a reference to a document, if that were the common ancestor. This may lead to memory bloat, however (mCommonDocument, mCommonAttribute, mCommonEntityRef, mCommonDocumentFragment, and who knows what else we'll need pointers for, most of which will be null). It's also not very scalable. | ||
=== Your Ideas Welcome Here === | === Your Ideas Welcome Here === | ||