But the interpreter isn't cleaning up the object, it's setting the
reference to undef. The object is still around (and accessible
by other means).
I like your recreational-swim analogy, but I'm still trying to
figure out how the behavior I'm seeing is consistent with the
specified operation of the garbage collector. The Camel book says that
objects are always destroyed in a separate pass before ordinary
references (3rd ed. page 331), and maybe that's a clue, but there's
still a problem:
When the interpreter is ready to exit, presumably "everything"
goes out of scope. At that point, there are no references left to my
$::index object. So it should be garbage collected pretty early. But
it's not and, worse, an object reference it's holding is set to undef
at some apparently arbritrary moment. I've been very careful to avoid
circular references, so there *is* a sensible destruction order for
these objects. But if references disappear without provocation, then
that order can't be maintained.
Posts are HTML formatted. Put <p> </p> tags around your paragraphs. Put <code> </code> tags around your code and data!
Read Where should I post X? if you're not absolutely sure you're posting in the right place.
Please read these before you post! —
Posts may use any of the Perl Monks Approved HTML tags:
You may need to use entities for some characters, as follows. (Exception: Within code tags, you can put the characters literally.)
- a, abbr, b, big, blockquote, br, caption, center, col, colgroup, dd, del, div, dl, dt, em, font, h1, h2, h3, h4, h5, h6, hr, i, ins, li, ol, p, pre, readmore, small, span, spoiler, strike, strong, sub, sup, table, tbody, td, tfoot, th, thead, tr, tt, u, ul, wbr
Link using PerlMonks shortcuts! What shortcuts can I use for linking?
See Writeup Formatting Tips and other pages linked from there for more info.
| & || & |
| < || < |
| > || > |
| [ || [ |
| ] || ] ||