Re: Undefining subroutines and inheritance

Maybe you have to delete the symbol-table hash key?

# UNTESTED!
# Instead of undef &{B::A}
delete $B::A::{CODE};
[download]

Update: Oh well. :-(

Update again! Ah-ha! This seems to work fine, even preserving $B::A (though I wouldn't think it would...):

# Instead of undef &{B::A}
delete $B::{A};
[download]

Can anyone explain why that doesn't seem to destroy $B::A? It seems dangerous and prone to breakage, so you should probably use chromatic's suggestion below.

bbfu
Seasons don't fear The Reaper.
Nor do the wind, the sun, and the rain.
We can be like they are.

Comment on Re: Undefining subroutines and inheritance Select or Download Code

Replies are listed 'Best First'.
Re: Re: Undefining subroutines and inheritance by bikeNomad (Priest) on Jun 29, 2001 at 00:25 UTC
Can anyone explain why that doesn't seem to destroy $B::A? Ah, but it seems to! Try replacing the bottom of the program with: `A->A; # Why doesn't it just call A::A here because of inheritance? B->A; # Not a CODE reference at noinherit.pl line 27. eval "print \$B::A"; # Use of uninitialized value in print at (eval 2) + line 1.` [download]	[reply] [d/l]
Re3: Undefining subroutines and inheritance by bbfu (Curate) on Jun 29, 2001 at 02:44 UTC
Hrm. I guess normal references to variables are bound at compile-time. Ah, well. Back to chromatic's method. shrug bbfu Seasons don't fear The Reaper. Nor do the wind, the sun, and the rain. We can be like they are.	[reply]
Re: Re: Undefining subroutines and inheritance by dragonchild (Archbishop) on Jun 28, 2001 at 23:55 UTC
Nope. I just tried it and it doesn't work. Nice thought, though...	[reply]