* Hans Dieter Pearcey <[EMAIL PROTECTED]> [2007-07-18T16:04:17] > On Wed, Jul 18, 2007 at 03:52:55PM -0400, Ricardo SIGNES wrote: > > I mean, do we want to use Moose? It always comes up, half in jest. I don't > > know what its performance or maintenance impact are. I don't think it adds > > *that* many prerequisites, but I haven't looked up the whole tree. > > Specifically, I keep bringing it up, because there are so many possible > different behaviors that you might want to mix together, especially once MIME > is involved, and Moose seems like a really solid framework for managing all of > that without a ridiculous number of subclasses (I'm thinking of Roles, in > particular).
Yeah, I think that any useful solution is going to be a form of roles, mixins, traits, or whatever you want to call those things. I just don't know whether it's Moose's implementation that will win out. I'm trying not to prototype any of this in my head in terms of email objects, because the minimum useful core is very large. I am fairly convinced that a core email object on which other behavior is hung will be MUCH more like Mail::Message than Email::Simple. Still, if the common code is going to support something on that order, then scalability is as important as lightness. -- rjbs
