Re: date() behaviour changed in 5.1?
| From: | Jochem Maas | Date: | Wed, 16 Nov 2005 12:24:33 +0000 |
| Subject: | Re: date() behaviour changed in 5.1? | ||
| References: | 1 2 3 4 5 6 7 8 9 10 | Groups: | php.internals |
| Request: | Send a blank email to internals+get-20062@lists.php.net to get a copy of this message | ||
Rasmus Lerdorf wrote:
Derick Rethans wrote:neither do I - and I garantee it will make PHP less attractive as a tool especially to the legions of 'noobs' that account for the popularity of php. (I throw the same argument at the changes made to array_merge() with regard to no longer accepting non-array values) I would suggest that psychologically any BC breakage and inconsitency introduced in the short to medium term hits twice as hard because of the reference related fixes/breaks/changes (which in itself is already a big hurdle for lots of developers and ISPs) - my point being that for the sake of the future wellbeing of the community someone should be stepping on the "Purism Brake" a little harder. the pragmatic ideal embodied in php since its conception is being somewhat eroded imho, and I don't see the point in creating a 'perfect' tool if only 10 people are capable of and want to use it. rgds, JochemOn Tue, 15 Nov 2005, Andrei Zmievski wrote:I don't like having two different ways to cast things and I think we would break a lot of stuff if (int)"123abc" no longer resulted in 123.Perhaps, but I would maintain that passing "123abc" and having it interpreted as 123 is still wrong.Yeah, I lean that way too, although trailing whitespace should be supported IMO.
-Rasmus