> 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. > I'm really not sure how far (if at all) we should go in trying to make > DateTime.pm suitable as a superclass for other calendars. Look at the > mess that is the Java datetime stuff, and note that they tried to do this > ;) We are agreed that we don't want the Java mess. :) What I'm concerned about it a lot of reimplementations of basically the same thing, i.e. part of the Java mess. 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). Cheers, -J --
