On Thu, 26 Jun 2003, Joshua Hoblitt wrote: > > Hmm, this is a problem. I'm really not sure subclassing makes that much > > sense here. At the very least, you probably need to provide your own > > new() method. > > The DT constructor is pretty large - not much fun.
It can be broken up into multiple pieces. I certainly don't object to that. > Specifically I was addressing the difficulties the validator code causes > for sub-classing. Making an interface for this code would at least > improve sub-classing and allow the business module (or DT::W::Validator) > to make even more stringent conditions. To me the whole point of the > validator code is to prevent errors and in the general case it does > that. Now lets fix it for the special cases (I just mentioned two, > there are probably more). I'm really not convinced that subclasses should be using DateTime's new() method. Especially not a subclass for a calendar that has 13 months! Maybe we need to figure out what the subclasses are using and factor that out into a separate module which can be used by DateTime and other calendar modules. -dave /*======================= House Absolute Consulting www.houseabsolute.com =======================*/
