But, actually, I was trying to come up with a way of defining MODIFY_CODE_ATTRIBUTES that didn't require all the conniptions that Attribute::Handler is going through. To create those wrappers and assign them to the symbol table Attribute::Handler defines a MODIFY_CODE_ATTRIBUTE method that generates a bunch of handlers that run at various compilation phases, some of which don't play well with mod_perl (as noted by Thilosophy). It also stores the coderefs it gets from parameters passed to MODIFY_CODE_ATTRIBUTES in a hash for later pairing up with names (see its _gen_handler_AH_(...) and findsym(...) functions).
It is pretty obvious now why Attribute::Handlers does all this: the implementers of the attribute facility left a construction site half built as Thilosophy so eloquently put it. Time? Release dates? Inability to come up with a robust consistent design? Who knows? The perldocs hint at the last issue, but one would have to search the developer archives to know for sure. In any case, we are left with various workarounds.
Thank you so much for taking the time to help me better understand this.
Best, beth
In reply to Re^6: Is there a way to access the name under which a subroutine was first defined?
by ELISHEVA
in thread Is there a way to access the name under which a subroutine was first defined?
by ELISHEVA
| For: | Use: | ||
| & | & | ||
| < | < | ||
| > | > | ||
| [ | [ | ||
| ] | ] |