On Fri, 8 Aug 2003, Flavio S. Glock wrote:
Dave Rolsky wrote:
Anyway, does this API sound sane? And if it does, anyone have any really
clever implementation ideas? I have some scary ones involved AUTOLOAD and
constructing classes on the fly.
help me understand it -
Does something
Anyway, does this API sound sane? And if it does, anyone have any really
clever implementation ideas? I have some scary ones involved AUTOLOAD and
constructing classes on the fly.
help me understand it -
Does something like DT::Incomplete could be a wrapping class?
No. This is the
On Fri, 9 Aug 2003, Rick Measham wrote:
On Sat, 2003-08-09 at 06:55, Dave Rolsky wrote:
So what I think we really want is this:
my $Wrapper = DT::Wrapper-wrapper( [$class1, $class2, $class3] );
Maybe my approach has some holes, but have a look at the attached and
see what you think
On Sat, 2003-08-09 at 06:55, Dave Rolsky wrote:
So what I think we really want is this:
my $Wrapper = DT::Wrapper-wrapper( [$class1, $class2, $class3] );
Maybe my approach has some holes, but have a look at the attached and
see what you think ...
#!/usr/bin/perl
On Friday, August 8, 2003, at 10:21 PM, Joshua Hoblitt wrote:
This is the 'decorator infrastructure' that I've been whining for.
It's kind of a melting pot for 'add-ons' or 'plug-ins'. The idea is
to throw DT, DT::Cache, DT::Foo, DT::Validator, etc. into the 'pot'
and end up with a factory
