The point is that, for instance, PHP 5.3 was not a trivial upgrade for coders or hosters. Sure it's mostly compatible, and you certainly can write code that works from 5.0->5.3 just fine, and if not then you're probably doing something wrong... but that's most of the PHP code out there right now. :-) And naturally you can't test your code against 5.3 until it's out.
Larry, to mitigate this issue, please refer to the exhaustive list of instructions here:
http://twitter.com/nateabele/status/10733251789
PLEASE NOTE: This also applies to user-land applications with test suites (and here I'm risking showing my ignorance by blindly assuming Drupal does, in fact, have a test suite).
Please see http://snaps.php.net/ and http://qa.php.net/ for more information.
Thanks,
- Nate
The point is that, for instance, PHP 5.3 was not a trivial upgrade for coders or hosters. Sure it's mostly compatible, and you certainly can write code that works from 5.0->5.3 just fine, and if not then you're probably doing something wrong... but that's most of the PHP code out there right now. :-) And naturally you can't test your code against 5.3 until it's out.
Larry, to mitigate this issue, please refer to the exhaustive list of instructions here:
http://twitter.com/nateabele/status/10733251789
PLEASE NOTE: This also applies to user-land applications with test suites (and here I'm risking showing my ignorance by blindly assuming Drupal does, in fact, have a test suite).
Please see http://snaps.php.net/ and http://qa.php.net/ for more information.
Thanks,
- Nate
Drupal 7 has an extensive test suite, using our own testing framework
rather than phpt. (Let's not get into a debate about why that's the
case; it's neither here nor there nor would I even be on just one side
of it. <g>)
But that's for a high-end project. It doesn't really help the code
slingers that happen to have code they threw together that is holding
back a hosting company who don't even know what "make" is.
I am not saying people shouldn't be testing code. I'm saying the
barrier to entry to testing common code found in the wild on a new
release of PHP is higher than you seem to be assuming.
--Larry Garfield
The point is that, for instance, PHP 5.3 was not a trivial upgrade
for coders or hosters. Sure it's mostly compatible, and you certainly
can write code that works from 5.0->5.3 just fine, and if not then
you're probably doing something wrong... but that's most of the PHP
code out there right now. :-) And naturally you can't test your code
against 5.3 until it's out.Larry, to mitigate this issue, please refer to the exhaustive list of
instructions here:http://twitter.com/nateabele/status/10733251789
PLEASE NOTE: This also applies to user-land applications with test
suites (and here I'm risking showing my ignorance by blindly assuming
Drupal does, in fact, have a test suite).Please see http://snaps.php.net/ and http://qa.php.net/ for more
information.Thanks,
- Nate
Drupal 7 has an extensive test suite, using our own testing framework
rather than phpt. (Let's not get into a debate about why that's the
case; it's neither here nor there nor would I even be on just one side
of it. <g>)But that's for a high-end project. It doesn't really help the code
slingers that happen to have code they threw together that is holding
back a hosting company who don't even know what "make" is.I am not saying people shouldn't be testing code. I'm saying the barrier
to entry to testing common code found in the wild on a new release of
PHP is higher than you seem to be assuming.--Larry Garfield
I think this has something to do with a large part of PHP developers
living in a Windows world, where aren't any good test suites (let alone
make).
PHPUnit is wonderful; installing it is not exactly that enjoyable.
Particularly nasty part is getting a working PEAR system on Windows.
(Just think of the BAT/CMD scripts :| )
--
Pas
The point is that, for instance, PHP 5.3 was not a trivial upgrade
for coders or hosters. Sure it's mostly compatible, and you certainly
can write code that works from 5.0->5.3 just fine, and if not then
you're probably doing something wrong... but that's most of the PHP
code out there right now. :-) And naturally you can't test your code
against 5.3 until it's out.Larry, to mitigate this issue, please refer to the exhaustive list of
instructions here:http://twitter.com/nateabele/status/10733251789
PLEASE NOTE: This also applies to user-land applications with test
suites (and here I'm risking showing my ignorance by blindly assuming
Drupal does, in fact, have a test suite).Please see http://snaps.php.net/ and http://qa.php.net/ for more
information.Thanks,
- Nate
Drupal 7 has an extensive test suite, using our own testing framework
rather than phpt. (Let's not get into a debate about why that's the
case; it's neither here nor there nor would I even be on just one side
of it. <g>)But that's for a high-end project. It doesn't really help the code
slingers that happen to have code they threw together that is holding
back a hosting company who don't even know what "make" is.I am not saying people shouldn't be testing code. I'm saying the barrier
to entry to testing common code found in the wild on a new release of
PHP is higher than you seem to be assuming.--Larry Garfield
I think this has something to do with a large part of PHP developers living
in a Windows world, where aren't any good test suites (let alone make).PHPUnit is wonderful; installing it is not exactly that enjoyable.
Particularly nasty part is getting a working PEAR system on Windows. (Just
think of the BAT/CMD scripts :| )--
Pas--
It seems that the
"Implement David's Circular Garbage collection patch" was not merged into
5.3, I think it should be a good feature for 5.4
Could you check this old old list, maybe there are other nice left-out
patches/ideas to pick up:
http://news.php.net/php.internals/32330
Tyrael
It seems that the
"Implement David's Circular Garbage collection patch" was not merged into
5.3, I think it should be a good feature for 5.4
Uh, yes it was. It's most definitely in 5.3.
Derick
--
http://derickrethans.nl | http://xdebug.org
Like Xdebug? Consider a donation: http://xdebug.org/donate.php
twitter: @derickr and @xdebug
sorry, my bad.
Tyrael
It seems that the
"Implement David's Circular Garbage collection patch" was not merged into
5.3, I think it should be a good feature for 5.4Uh, yes it was. It's most definitely in 5.3.
Derick
--
http://derickrethans.nl | http://xdebug.org
Like Xdebug? Consider a donation: http://xdebug.org/donate.php
twitter: @derickr and @xdebug
The point is that, for instance, PHP 5.3 was not a trivial upgrade for coders or hosters. Sure it's mostly compatible, and you certainly can write code that works from 5.0->5.3 just fine, and if not then you're probably doing something wrong... but that's most of the PHP code out there right now. :-) And naturally you can't test your code against 5.3 until it's out.
Larry, to mitigate this issue, please refer to the exhaustive list of instructions here:
http://twitter.com/nateabele/status/10733251789
PLEASE NOTE: This also applies to user-land applications with test suites (and here I'm risking showing my ignorance by blindly assuming Drupal does, in fact, have a test suite).
Please see http://snaps.php.net/ and http://qa.php.net/ for more information.
Thanks,
- Nate
Most actively developed apps out there are targeting very recent PHP
versions and generally are aware of changes, (especially when it comes
to backward incompatibility) and try to emulate features for older
versions. (Like get_called_class().)
Also, any competent hosting provider allows customers to choose PHP
version. (DreamHost for example allow it on a per (sub)domain basis.)
--
Pas