Name: gsC80088 Date: 03/11/99
Calendar is one of the most unintuitive classes
i've ever used. There's really no need for this complexity.
Unfortunately, instead of simplifying this class,
I've noticed you instead added even more complexity.
I assume the timestamps are there to address the problems
people run into when using this class. But I'm afraid,
it just makes things worse. Because there is no way to
retrieve this time stamp information, there's no way
to predict what results the object will give you.
(however, please don't make the timestamps available!!!)
Please consider making the class more intuitive.
The easiest solution is to elimate the notion of unset
fields and inconsistent state. Make the state *always*
consistent. In other words, modify or remove all methods
that might make the calendar state inconsistent. At
any point in time, all calendar fields are available and
(Review ID: 52400)