On Tuesday 12 October 2004 11:35, Jeroen Frijters wrote: > Michael Koch wrote: > > On Monday 11 October 2004 15:39, Jeroen Frijters wrote: > > > I have some code that depends on unspecified behavior of > > > java.util.Date. In the Sun JDK if you pass out of range > > > parameters to the Date constructors that take year, month, > > > date, etc. it will automatically convert to a valid date (for > > > example, new Date(104, 8, 41) is Oct 11, 2004.) > > > > > > I have a rather lame patch that addresses this (see below), > > > would anyone object to this? > > > > Are there mauve test that confirm that this breaks nothing ? > > I made a new Mauve test (attached) that works better with my patch > (after I fixed one error in my patch and fixed an additional Date > bug), but it still fails on three tests. One is due to a bug in > GregorianCalendar and I haven't investigated the other two. > > Is the attached test OK to commit? Do I need to modify any other > Mauve files to add the test?
Just add the file with a proper ChangeLog entry and be done. Thats all you need to do. Thanks for the testcase. Michael _______________________________________________ Classpath mailing list [EMAIL PROTECTED] http://lists.gnu.org/mailman/listinfo/classpath
