On Fri, Jul 16, 2010 at 04:10:10PM +1000, Rick Measham wrote: > ... disconnect between calculation and representation. > DateTime's strength is it's rigid adherence to being Correct.
Right and the DateTime::Duration object isn't the right object to do what I want since it doesn't have the information I want (rigidly speaking). Still... If $date1 and $date2 contain specific dates and times. Then the conversion to $duration = ($date1-$date) has chosen to lose the information I was seeking during the instantiation. It was possibly to know the number of seconds (without ambiguity) before the internal representation was chosen. Is that representation rigidly correct? Clearly the DateTime::Duration is rigidly correct, but is the overloading? Something still doesn't seem right to me; but I'm clearly in the wrong here. Cheers again, -Paul -- If riding in an airplane is flying, then riding in a boat is swimming. 116 jumps, 48.6 minutes of freefall, 92.9 freefall miles.
