in reply to Re: undefining one slot of a typeglob
in thread undefining one slot of a typeglob

it didn't occur to me that i didn't have to use a typeglob as my holder. good idea, and although it's a core module, this approach means i have one less use statement. Can anybody tell me why do this:
if ($type eq 'SCALAR') { undef ${*{$glob}} ;} elsif ($type eq 'ARRAY') { undef @{*{$glob}} ;} elsif ($type eq 'HASH') { undef %{*{$glob}} ;} elsif ($type eq 'CODE') { undef &{*{$glob}} ;} elsif ($type eq 'IO') { close *{$glob} ;}
instead of this:
($type eq 'IO') ? close *{$glob} : undef *{$glob}{$type};
and i have to wonder if just using this would not work:
undef *{$glob}{$type};
update: I should note that completely eradicating the sub from memory isn't necessarily the problem here, as sometimes the created CODE glob is simply an alias from another package rather than a brand new anonymous sub.

Replies are listed 'Best First'.
Re: Re: Re: undefining one slot of a typeglob
by gmpassos (Priest) on Feb 24, 2004 at 08:24 UTC
    If I'm not wrong we can't change a glob key/element, only access it. Soo, this won't work:
    undef *{$glob}{$type} ;
    And I make this:
    if ($type eq 'SCALAR') { undef ${*{$glob}} ;} elsif ($type eq 'ARRAY') { undef @{*{$glob}} ;} elsif ($type eq 'HASH') { undef %{*{$glob}} ;} elsif ($type eq 'CODE') { undef &{*{$glob}} ;} elsif ($type eq 'IO') { close *{$glob} ;}
    Not to remove the element from the GLOB, but to ensure that it goes out of the memory, since undef *{$glob} already remove all the keys/elements. Actually for your needs you can remove all the if ( $type eq '...' ).

    Graciliano M. P.
    "Creativity is the expression of the liberty".