I said: > Maybe new() takes an optional ISOyear parameter? Thus the > default 'year' is the way we commonly think of it and can take > optional BC/BCE/AD/CE coding. It treats -1 as 1 BC and dies on > getting '0'. ISOyear can only take integers with an optional > '-'.
On 13/2/03 9:13 am, Peter J. Acklam at [EMAIL PROTECTED] replied: > I like that idea. However, ISOyear must allow a leading '+' if > years after 9999 are supported. ISO 8601 states that all years > outside [0000,9999] must be signed. Thanks for your support for the idea Peter, but I hereby withdraw it: On 13/2/03 9:05 am, Dave Rolsky at [EMAIL PROTECTED] spake thus: > This is why there will be a DateTime::Format::ISO8601 module for parsing > ISO formats ;) The standard module won't need special handling for ISO, its just a case of using the right Format module. Cheers! Rick Measham -------------------------------------------------------- �� � � � � � There are 10 kinds of people: �� those that understand binary, and those that don't. -------------------------------------------------------- �� The day Microsoft makes something that doesn't suck �� � is the day they start selling vacuum cleaners --------------------------------------------------------
