Re^4: Garbage collection at subroutine return

No need to really even do that. Use references and have DoIt return the reference:

my $h = DoIt( $max );
sub DoIt{
        my $limit=shift;
        my $i;
        my $myhash;
        foreach $i (0..$limit){
                $myhash->{$i}=1;
        }
        $func_done = (times)[0];
        $myhash;
}
[download]

That prevents the reference count from being decremented and hence no gc (well at least tell the end of the block containing $h)

-derby

Comment on Re^4: Garbage collection at subroutine return Download Code

Replies are listed 'Best First'.
Re^5: Garbage collection at subroutine return by RMGir (Prior) on Feb 16, 2007 at 15:06 UTC
True, but slightly different. Your approach is correct if the goal is to construct a one-off structure and pass it back to the caller, surviving until the caller is done with it. Useful if the function generates some kind of custom hash mapping, for example. My approach is correct if the intent of myhash is to be some kind of persistent structure internal to the mechanics of DoIt, perhaps some kind of memoization cache or other internal structure. They're both useful, it all depends on what the original intent was (which is a bit hard to discern from the question). Mike	[reply]

Replies are listed 'Best First'.

Re^5: Garbage collection at subroutine return
by RMGir (Prior) on Feb 16, 2007 at 15:06 UTC

Your approach is correct if the goal is to construct a one-off structure and pass it back to the caller, surviving until the caller is done with it. Useful if the function generates some kind of custom hash mapping, for example.

My approach is correct if the intent of myhash is to be some kind of persistent structure internal to the mechanics of DoIt, perhaps some kind of memoization cache or other internal structure.

They're both useful, it all depends on what the original intent was (which is a bit hard to discern from the question).

Mike

[reply]