- From: <bugzilla@jessica.w3.org>
- Date: Wed, 29 Sep 2010 18:59:49 +0000
- To: public-html-bugzilla@w3.org
http://www.w3.org/Bugs/Public/show_bug.cgi?id=10834
Ian 'Hixie' Hickson <ian@hixie.ch> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |ian@hixie.ch
--- Comment #1 from Ian 'Hixie' Hickson <ian@hixie.ch> 2010-09-29 18:59:49 UTC ---
This stuff is only specified because it is observable. For example, if you
create a document using createDocument, then create an Element using
createElement on that document, then drop all references to everything except
the element, element.ownerDocument has to remain non-null, and the only reason
for that as far as I can tell is because the spec says that there's a strong
reference there.
What kinds of garbage collection algorithms are based on anything other than
whether anything references an object? I mean there's lots of ways of doing
that, sure, but don't they all boil down to inferring state from the current
set of references?
--
Configure bugmail: http://www.w3.org/Bugs/Public/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the QA contact for the bug.
Received on Wednesday, 29 September 2010 18:59:51 UTC