Thanks for asking. I'm a zelot on timely destruction, and
have been meaning to lobby for not dropping it in Perl
6!
Cool, then. Give me examples of things that'll break without timely
finalization!
If there is a performance issue, at least make it optional.
Ah, therein lies the rub. You can't make something like this
optional. It's either there, with full support for it, or it's not
there. There is no optional here. (If there was, I'd not be asking
this question)
Unfortunately none of the things you've presented quite do
it. Filehandles will be cleaned up reasonably quickly. Windows
definitely ought not go missing without some active action on the
part of a program. And "after" semantics on objects when they get
destroyed, well, you get that. It's just potentially indeterminate
when it happens. (Which, I realize, is the issue)
I think if the compiler could emit code that says "exit
scope; if referece count of the variable reached zero, then call
function" then it can take it from there.
There are no reference counts in parrot, and thus none in perl 6. If
there were this wouldn't be an issue.
-
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.
|
