I believe that if you parse "23:00:00", you want the hour that is called "23:00", not the "23'rd hour". Especially if they are different.
/ Marcus Comstedt (ACROSS) (Hail Ilpalazzo!)
Previous text:
2003-03-30 14:20: Subject: Calendar failure
Calendar.parse("%Y-%M-%D %h:%m:%s %z","2003-03-30 23:00:00 Europe/Stockholm");
(5) Result: 0
That is bad. It's probably from the fact that the 23'rd hour doesn't exist 03-30 (see below), but it's still bad. I can't believe noone noticed before?
Calendar.Second(2003,3,30,2,0,0);
(7) Result: Second(Sun 30 Mar 2003 3:00:00 CEST)
This might be a design fault; but the second hour *is* called "3:00". The parse() function corrects this to match the data, but the Second/Minute/Hour constructors doesn't seem to.
Should they?
/ Mirar