[PHP-DEV] question about backward-compatibility break/bug in php 5.2.6

Hello all, Last week I submitted a bug report on the issue described below. The response (also below) was that this is not a bug. I fail to see how it could *not* be a bug given that strtotime is parsing an invalid date into a seemingly-arbitrary and definitely-meaningless number, rather than re

Re: [PHP-DEV] question about backward-compatibility break/bug in php 5.2.6

> Hello all, > > Last week I submitted a bug report on the issue described below. The > response (also below) was that this is not a bug. I fail to see how it > could *not* be a bug given that strtotime is parsing an invalid date > into a seemingly-arbitrary and definitely-meaningless number, rat

Re: [PHP-DEV] question about backward-compatibility break/bug in php 5.2.6

Hi, Last week I submitted a bug report on the issue described below. The response (also below) was that this is not a bug. I fail to see how it could *not* be a bug given that strtotime is parsing an invalid date into a seemingly-arbitrary and definitely-meaningless number, strtotime() has a

RE: [PHP-DEV] question about backward-compatibility break/bug in php 5.2.6

> Ah, yes, the change responsible is the following: > > r1=1.10.2.11.2.4&r2=1.10.2.11.2.5&pathrev=PHP_5_2> > > It fixes bug #44209 . OK, thanks, it's good to understand the change in behavior

Re: [PHP-DEV] question about backward-compatibility break/bug in php 5.2.6

Hi! This 64-bit machine is running 5.2.5 and returns false on the all-zero datetime string. It was upgraded last week to 5.2.6 and started returning the large negative integer. Ah, yes, the change responsible is the following:

Re: [PHP-DEV] question about backward-compatibility break/bug in php 5.2.6

I'm not sure that there's any problem with the documentation (although it wouldn't hurt to mention it in the comments). What is it about "-00-00 00:00:00" that makes it an invalid date? (See Christian's explanation) Zach On Thu, Jul 24, 2008 at 11:09 AM, Jack Steadman <[EMAIL PROTECTED]> wrot

RE: [PHP-DEV] question about backward-compatibility break/bug in php 5.2.6

> I'm not sure that there's any problem with the documentation > (although it wouldn't hurt to mention it in the comments). > What is it about "-00-00 00:00:00" that makes it an > invalid date? (See Christian's explanation) Zero values for month and day are NOT valid. PHP treats them as v

RE: [PHP-DEV] question about backward-compatibility break/bug in php 5.2.6

Thank you for taking the time to explain this to me. A couple more points below: > strtotime() has always accepted month and day numbers 0 in order to > express "last month of the previos year" and "last day of the previous > month". Take: So my biggest issue with this is that it's exception-cas

Re: [PHP-DEV] question about backward-compatibility break/bug in php 5.2.6

On Jul 24, 2008, at 11:30 AM, Jack Steadman wrote: The upshot is that we can't actually rely on strtotime to determine whether a string is a valid date/time. The docs don't ever explicitly say that the date strings themselves are checked for validity, but returning false on "failure" implies to

RE: [PHP-DEV] question about backward-compatibility break/bug in php 5.2.6

On Thu, 24 Jul 2008, Jack Steadman wrote: > Thank you for taking the time to explain this to me. A couple more > points below: > > > strtotime() has always accepted month and day numbers 0 in order to > > express "last month of the previos year" and "last day of the previous > > month". Take: >