Larry Jones wrote:
Yes, the checkout command is failing, but that's because the test isYou could argue for February 28th (or 29th in a leap year), for that matter. End of October + 100 months = end of February. That's probably the one I'd pick.
deficient, not CVS. I suppose it's a matter of perspective: If you
naively add 100 months to October 31, 2002, you get February 31, 2011,
which is an invalid date. That's what currently happens, so you get an
error that the specified date is invalid ("Can't parse date/time"). A
more sophisticated addition could be used to come up with a valid date,
but which one? One could make a good argument for either March 1 or
March 3, but either one is apt to be surprising to some people. Since
there's no single, obviously correct answer, I think producing an error
is the right thing to do.
-Larry Jones
Hmm... That might not be politic. -- Calvin
What about setting errno in getdate.y and setting a string to the unparsable date or more likely setting a global error string to a complete error message including the invalid date. I think "Date/time resolves to non-existant date: Feb. 30, 2004" is much more user-friendly than "Can't parse date/time: 100 months", which is almost the same error message I'd get if I asked CVS to parse "asdfkhjgfadlhglfj" as a date.
Derek
--
*8^)
Email: [EMAIL PROTECTED]
Get CVS support at <http://ximbiot.com>!
_______________________________________________
Bug-cvs mailing list
[EMAIL PROTECTED]
http://mail.gnu.org/mailman/listinfo/bug-cvs
