> > 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 '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 that creates object with features from all of the input classes. -J --
