in reply to use Very::Long::Module::Name as Foo;
. . . bart's response (which is the simple assignment of @ISA) . . .
I'd like to use this as cannon fodder against those who said modifying @ISA directly is OK here. My argument in that meditation was that directly assigning @ISA is bad because it clobbers any existing values, and that one should always use base instead, if possible. Many posters in that thread noted that nobody else should be messing with your package's @ISA. At the time, I couldn't come up with a good reason why an external source would be playing with your @ISA, but thought there might be a good reason that I hadn't seen yet. Now I have one. Thanks :)
I'd like to take this opertunity to say na na na, your it, no returns.
----
I wanted to explore how Perl's closures can be manipulated, and ended up creating an object system by accident.
-- Schemer
Note: All code is untested, unless otherwise stated
|
|---|