> 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 returning false as it is supposed to. Can someone explain to me > why this is "intended" behavior? We do rely on strtotime returning > false on invalid dates, and this behavior changed between 5.2.5 and > 5.2.6. Do we need to update our code to check for this arbitrary > negative integer? I would prefer not to do that.
Date is not invalid. Some diety was born at -62169966000 Unixtime. -- Tomas -- PHP Internals - PHP Runtime Development Mailing List To unsubscribe, visit: http://www.php.net/unsub.php
