NOTE: use Perl; is on undef hiatus. You can read content, but you can't post it. More info will be forthcoming forthcomingly.
All the Perl that's Practical to Extract and Report
--Larry Wall in perl.c from the perl source code
Stories, comments, journals, and other submissions on use Perl; are Copyright 1998-2006, their respective owners.
You are totally mistaken in your assumptions (Score:1)
There is no violation of encapsulation here actually, you should ask before you assume :)
Class::MOP::Instance [cpan.org] is the meta object which represents the instance structure, it is the gateway through which all the access to the underlying instance structure is proxied (it also handles generating code for any inlined accessors as well). This puts a layer of abstraction over the instance structure so that the Moose user does not have to think about what kind of instance they are using, and therefore can chang
Re: (Score:2)
What did you think my assumptions were, Stevan? I wasn't assuming this would pass. I was merely hoping I could get away with it :)
Re:You are totally mistaken in your assumptions (Score:1)
From your title ("Encapsulation or Moose"), and your initial line ("This was not surprising, but also not what I wanted" ) it seemed to me that you were implying that Moose violated encapsulation. Which admitedly, if you go by the definition of encapsulation encoded in Devel::Encapsulation, it does. However, there is more than one way to do it :)
Of course, my response is riddled with assumptions on my part, so if I am mistaken, please clarify it for me.
- Stevan
Reply to This
Parent