> -----Original Message----- > From: James Duncan Davidson [mailto:[EMAIL PROTECTED] > There's enough functionality that can be implemented in Project, > Target, and > Task to merit them being classes. And, since it's not expected that there > will be multiple differing implementations of Project, Target, and Task > (note that the Task is a fa�ade that hides the AbstractTask implementation > behind it in AntEater) I don't think that the complexity with making these > interfaces with backing classes is worth the extra code and obscurity.
I think that just the opposite can make for an interesting design. If *everything* is simply a Task, the design gets so simple its scary! jim
