Hi,
On Thu, Feb 23, 2012 at 5:57 AM, Bill Moseley mose...@hank.org wrote:
I often have classes that abstract out the work of fetching data from
multiple sources -- so I have attributes that hold instances of the objects
that do the actual work. Each of these objects need their own config.
On Thu, 23 Feb 2012 11:27:18 +
Pedro Melo m...@simplicidade.org wrote:
Hi,
On Thu, Feb 23, 2012 at 5:57 AM, Bill Moseley mose...@hank.org
wrote:
I often have classes that abstract out the work of fetching data
from multiple sources -- so I have attributes that hold instances
of the
On Thu, Feb 23, 2012 at 12:57:26PM +0700, Bill Moseley wrote:
I often have classes that abstract out the work of fetching data from
multiple sources -- so I have attributes that hold instances of the objects
that do the actual work. Each of these objects need their own config.
I've used
On Thu, 23 Feb 2012, Dave Rolsky wrote:
You could do it as a parameterized role, maybe:
with 'Role::Container' =
{ contains = { bar = 'Foo::Bar', baz = 'Baz::Object' } );
This would introspect the relevant classes and either add attributes or some
sort of BUILD or BUILDARGS wrapper to
