On 1/5/10 2:15 PM, Karen Etheridge wrote:
> Will MI still be required after your refactoring, or are you saying that
> your described approach will not work until the refactoring is done?
Uploaded 0.15 with said refactoring. I don't want to take the fun out of
figuring out how all the pieces fit t
Excerpts from Karen Etheridge's message of Tue Jan 05 14:15:40 -0500 2010:
> > You'll have multiple inheritance, which obviously sucks. I'm sorry for
> > my half of that. It will be straightforward for me to refactor the guts
> > of MooseX::Role::Parameterized::Meta::Role::Parameterizable (which is
On 1/5/10 2:15 PM, Karen Etheridge wrote:
>> You'll have multiple inheritance, which obviously sucks. I'm sorry for
>> my half of that. It will be straightforward for me to refactor the guts
>> of MooseX::Role::Parameterized::Meta::Role::Parameterizable (which is
>> just two attributes) into a role
On Tue, Jan 05, 2010 at 01:33:41PM -0500, Shawn M Moore wrote:
> Hopefully that makes some amount of sense. You have a lot of
> metaprogramming ahead of you. Good luck and feel free to ask plenty more
> questions.
Awesome! When I get this nasty deadline out of the way I'll play around and
see what
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 1/4/10 10:38 PM, Karen Etheridge wrote:
> What would it take to gain the properties of MooseX::Role::Strict in
> MooseX::Role::Parameterized? I've been using strict roles everywhere and
> love them -- they've caught a few bugs that I'm sure would h
--- On Tue, 5/1/10, Karen Etheridge wrote:
> From: Karen Etheridge
> What would it take to gain the properties of
> MooseX::Role::Strict in
> MooseX::Role::Parameterized? I've been using strict
> roles everywhere and
> love them -- they've caught a few bugs that I'm sure would
> have been
> dr
