## [Jython-dev] Re: Why was the date 0000-00-00 converted to 2002-11-30 ?

 [Jython-dev] Re: Why was the date 0000-00-00 converted to 2002-11-30 ? From: Samuele Pedroni - 2002-07-22 16:41:35 ``` >Because: > >0000 = unspecified year = current year = 2002 0000 = 0002 [garbage] != 2002 :) valid years are in the range 1- Samuele. PS: yes, one could check the actual computation in GregorianCalendar but is not the point :) yes, the subject of the thread is incorrect :) ```

 [Jython-dev] Re: Why was the date 0000-00-00 converted to 2002-11-30 ? From: Samuele Pedroni - 2002-07-22 16:41:35 ``` >Because: > >0000 = unspecified year = current year = 2002 0000 = 0002 [garbage] != 2002 :) valid years are in the range 1- Samuele. PS: yes, one could check the actual computation in GregorianCalendar but is not the point :) yes, the subject of the thread is incorrect :) ```
 [Jython-dev] Re: Why was the date 0000-00-00 converted to 2002-11-30 ? From: Kevin J. Butler - 2002-07-22 18:12:22 ```Samuele Pedroni wrote: > >Because: > > > >0000 = unspecified year = current year = 2002 > > 0000 = 0002 [garbage] != 2002 :) Didn't even notice that - so much for that hypothesis! > valid years are in the range 1- > PS: yes, one could check the actual computation > in GregorianCalendar but is not the point :) But it is interesting! The date is actually correct, but the default date format loses important data: >>> sdf.calendar.getTime() Sun Nov 30 00:00:00 MST 0002 >>> sdf.calendar.get( c.ERA ) 0 >>> sdf.calendar.get( c.YEAR ) 1 0000 = 1 AD - 1 == 1 BC (year 0 does not exist) 00 = January of 1 BC - 1 = December of 2 BC 00 = December 1 - 1 = November 30th Cool. :-) kb ```