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.
-
Are you posting in the right place? Check out Where do I post X? to know for sure.
-
Posts may use any of the Perl Monks Approved HTML tags. Currently these include the following:
<code> <a> <b> <big>
<blockquote> <br /> <dd>
<dl> <dt> <em> <font>
<h1> <h2> <h3> <h4>
<h5> <h6> <hr /> <i>
<li> <nbsp> <ol> <p>
<small> <strike> <strong>
<sub> <sup> <table>
<td> <th> <tr> <tt>
<u> <ul>
-
Snippets of code should be wrapped in
<code> tags not
<pre> tags. In fact, <pre>
tags should generally be avoided. If they must
be used, extreme care should be
taken to ensure that their contents do not
have long lines (<70 chars), in order to prevent
horizontal scrolling (and possible janitor
intervention).
-
Want more info? How to link
or How to display code and escape characters
are good places to start.
|
