|
in reply to Re: Re (tilly) 1: Strict, strings and subroutines
in thread Strict, strings and subroutines
But you still don't avoid pulling in UNIVERSAL. Which is why I left it at, "It does something different." If you don't understand what you are doing differently and don't have a reason for it, well then you don't need to do this. But then again that is true for most of these solutions... :-) |
Re: Re (tilly) 3: Strict, strings and subroutines
by gbarr (Monk) on Oct 10, 2001 at 19:12 UTC
|
Unless someone has a strange perl configuration, UNIVERSAL is statically linked.
So you don't pull in UNIVERSAL, it is just there. | [reply] |
|
|
I possibly was unclear.
I meant pulling in UNIVERSAL in that functions which exist in UNIVERSAL but not in the current package would be found by merlyn's can invocation, even though you might not want them to be. In other words his local @ISA trick doesn't quite succeed in making a method lookup into a function lookup because it still finds things in UNIVERSAL.
| [reply] |
|
|
Ah, right. Yes that is true. For example, __PACKAGE__->can('can') will always return a code reference.
| [reply]
[d/l] |
|
