Re: [PHP-DEV] Re: PHP 5.4 branch and trunk

2010-03-23 Thread Ferenc Kovacs
On Sat, Mar 20, 2010 at 4:58 AM, Pas pasthe...@gmail.com wrote:

 On 2010.03.19. 19:50, la...@garfieldtech.com wrote:

 On 3/19/10 1:31 PM, Nate Abele wrote:

 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


 --
 PHP Internals - PHP Runtime Development Mailing List
 To unsubscribe, visit: http://www.php.net/unsub.php

 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


Re: [PHP-DEV] Re: PHP 5.4 branch and trunk

2010-03-23 Thread Derick Rethans
On Tue, 23 Mar 2010, Ferenc Kovacs wrote:

 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

-- 
PHP Internals - PHP Runtime Development Mailing List
To unsubscribe, visit: http://www.php.net/unsub.php



Re: [PHP-DEV] Re: PHP 5.4 branch and trunk

2010-03-23 Thread Ferenc Kovacs
sorry, my bad.

Tyrael

On Tue, Mar 23, 2010 at 2:18 PM, Derick Rethans der...@php.net wrote:

 On Tue, 23 Mar 2010, Ferenc Kovacs wrote:

  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



[PHP-DEV] Re: PHP 5.4 branch and trunk

2010-03-19 Thread Nate Abele
 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


--
PHP Internals - PHP Runtime Development Mailing List
To unsubscribe, visit: http://www.php.net/unsub.php



Re: [PHP-DEV] Re: PHP 5.4 branch and trunk

2010-03-19 Thread la...@garfieldtech.com

On 3/19/10 1:31 PM, Nate Abele wrote:

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

--
PHP Internals - PHP Runtime Development Mailing List
To unsubscribe, visit: http://www.php.net/unsub.php



Re: [PHP-DEV] Re: PHP 5.4 branch and trunk

2010-03-19 Thread Pas

On 2010.03.19. 19:31, Nate Abele wrote:

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().)


http://qa.drupal.org/

Also, any competent hosting provider allows customers to choose PHP 
version. (DreamHost for example allow it on a per (sub)domain basis.)


--
Pas

--
PHP Internals - PHP Runtime Development Mailing List
To unsubscribe, visit: http://www.php.net/unsub.php



Re: [PHP-DEV] Re: PHP 5.4 branch and trunk

2010-03-19 Thread Pas

On 2010.03.19. 19:50, la...@garfieldtech.com wrote:

On 3/19/10 1:31 PM, Nate Abele wrote:

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

--
PHP Internals - PHP Runtime Development Mailing List
To unsubscribe, visit: http://www.php.net/unsub.php



[PHP-DEV] Re: PHP 5.4 branch and trunk

2010-03-16 Thread David Soria Parra
On 2010-03-16, Derick Rethans der...@derickrethans.nl wrote:
 - Declare 5.2 security fixes only (Something for Ilia to declare).
 - Declare 5.3 bug fixes only (and ini-mini features if so desired) 
   (Something for Johannes to declare).

 Once that's done, I'd like to:

 - Recreate trunk from the 5.3 branch.

 - the new output buffering mechanism (I can not really see why we would 
   not want this)
is there something about that in the wiki? I think a few lines in the wiki
about this would be good.

 - Scott's big number improvements. Scott, can you explain (in an RFC) 
   what exactly this does and how it works?
 - Ilia's scalar type hint patch. There are RFCs:
   http://wiki.php.net/rfc/typechecking
 - traits, there are also RFCs:
   http://wiki.php.net/rfc/horizontalreuse
   http://wiki.php.net/rfc/nonbreakabletraits

thank you.

I agree that we should discuss new additions with proper rfcs before we commit
them. in addition to that peopled interested in unicode should get together and
discuss how to readd unicode support and in which way to do this.

-- 
PHP Internals - PHP Runtime Development Mailing List
To unsubscribe, visit: http://www.php.net/unsub.php



Re: [PHP-DEV] Re: PHP 5.4 branch and trunk

2010-03-16 Thread Hannes Magnusson
On Tue, Mar 16, 2010 at 17:10, David Soria Parra s...@gmx.net wrote:
 On 2010-03-16, Derick Rethans der...@derickrethans.nl wrote:
 - Declare 5.2 security fixes only (Something for Ilia to declare).
 - Declare 5.3 bug fixes only (and ini-mini features if so desired)
   (Something for Johannes to declare).

 Once that's done, I'd like to:

 - Recreate trunk from the 5.3 branch.

 - the new output buffering mechanism (I can not really see why we would
   not want this)
 is there something about that in the wiki? I think a few lines in the wiki
 about this would be good.

I doubt it. Its a rewrite which had to be done to simplify things and
fixes several bugs.


-Hannes

--
PHP Internals - PHP Runtime Development Mailing List
To unsubscribe, visit: http://www.php.net/unsub.php