in reply to Re: A couple questions on Moose::MOP::Class
in thread A couple questions on Moose::MOP::Class

Re Class::MOP::Method::Wrapped: Out of curiosity, does it gather all the before/after/around stuff into one thoughtful list, or does it just keep chaining things with more single-use wrappers?

And I was wondering... how does an 'after' method get called without having the wrapper show up in the call stack? If the original is chained to with a GOTO, it won't get control back again.

Moose and Class::MOP make a distinction between methods defined in your class, and functions imported from other modules.
Yea, that's what "no moose" and "autoclean" is all about. So, the method enumerator does the same thing as autoclean, and they work by comparing the name recorded in the function itself with the name it's being accessed under, to tell if it was not imported.

Let me see if I'm following... for code that's been generated or otherwise not created using the classic 'sub' at package level, it won't record that origin and would always look like it was imported, even for generated methods like the accessors. So what that passage was trying to say is that a fully-quallified name in the Sub::Name or the natural origin of the function is used to determine if it was imported. Right?

From reading Sub::Name, I thought that it simply records what you wanted in the same spot that a natural born sub does anyway. You talk about "B" and "stash" and other things not in my namespace, which makes me think now that the determination of the natural born name was not something it was originally meant to do. So Sub::Name is a newer thing and Carp et al. were updated to look at it, but defining a sub still doesn't populate that itself?

Re Welcome to the twisty maze: Thanks.