in reply to Re^2: RFC: Sub::Prepend - Prepend code to named subroutines
in thread RFC: Sub::Prepend - Prepend code to named subroutines
Actually, both the implication of permanent attachment and spatial rather than temporal seem to fit. The first is clear cut--it is a permanent modification, unlike some of the other modules that support unwrapping.
The second is more of how you think about it. I think about it as a code block that's inserted at the very beginning, i.e. "as a string", so
is equivalent toprepend foo => sub { # Remove the invocant. shift; }; sub foo { print shift; }
That doesn't mean I'm set on prepend. Spelled-out suggestions are still welcome.sub foo { { # Remove the invocant. shift; } print shift; }
lodin
|
---|
In Section
Meditations