Hi!
> Sorry, I missed that one. I suspect it was the time where I
> misconfigured git and branches did not get merged. Feel free to merge
> it back/backport as I won't be able to do it before Monday.
OK, I have backported it (and following Anatol's patches for it).
--
Stanislav Malyshev, Softwa
Hi!
> PHP 5.3 has reached the real end of life. Will the effect be that from
> now on PHP 5.4 will only get security fixes?
There's no dependency between the two in the release RFC, but it would
probably make sense to move 5.4 into "security only" phase once 5.6 is
GA, and set EOL date for 1 year
On 15 Aug 2014, at 02:06, Levi Morrison wrote:
>> As PHP 7 may break backwards-compatibility, 5.7 gives us a chance to add
>> deprecation warnings and such to help people prepare for 7.
>
> The updated multiple default blocks in a switch statement proposes
> exactly this. Even if PHP 5.7 doesn
> As PHP 7 may break backwards-compatibility, 5.7 gives us a chance to add
> deprecation warnings and such to help people prepare for 7.
The updated multiple default blocks in a switch statement proposes
exactly this. Even if PHP 5.7 doesn't have any features I think it
would make the transition
Good evening,
I’ve kept putting this off, but given the current “move phpng to master” vote,
I really can’t delay this any longer.
It looks like PHP 7 is going to happen and phpng will be the base of that.
While we could move straight to PHP 7 after the release of PHP 5.6, I think
there is som
Hi all,
On Wed, Jul 30, 2014 at 9:35 PM, Rowan Collins
wrote:
>
>- Consistent naming
>> - Consistent parameter order
>> - Graceful function/class/interface deprecation
>> (We know what we should do for these, right?)
>>
>
> I'm not sure if this was meant sincerely, or slightly tongue-in-
Chris Wright in php.internals (Thu, 14 Aug 2014 22:55:09 +0100):
>The release of 5.6 should push 5.4 into security-only state, rather
>than the 5.3 EOL. I realise in this case it should happen at almost
>the same time (I think the plan is that 5.6.0RC3 is the last RC?) ...
There will be a 5.6.0RC4
On 08/14/2014 01:43 PM, Keyur Govande wrote:
> Hello,
>
> I've opened https://github.com/php/php-src/pull/770 for patches for bugs
> #65463, #66036. More details in the PR.
>
> The bug is reproducible on PHP 5.4, 5.5 and 5.6 with and without
> --enable-zend-signals.
>
> Please review, I'm hesita
On 14 August 2014 22:41, Andrea Faulds wrote:
>
> On 14 Aug 2014, at 22:34, Jan Ehrhardt wrote:
>
>> PHP 5.3 has reached the real end of life. Will the effect be that from
>> now on PHP 5.4 will only get security fixes?
>
> I’m curious about this too. The release process RFC says only bug fixes a
On 14 Aug 2014, at 22:34, Jan Ehrhardt wrote:
> PHP 5.3 has reached the real end of life. Will the effect be that from
> now on PHP 5.4 will only get security fixes?
I’m curious about this too. The release process RFC says only bug fixes after 2
years, and it is well beyond that now (5.4 came
PHP 5.3 has reached the real end of life. Will the effect be that from
now on PHP 5.4 will only get security fixes?
Jan
--
PHP Internals - PHP Runtime Development Mailing List
To unsubscribe, visit: http://www.php.net/unsub.php
Oops.. somehow I only sent the reply to Levi.. I blame my phone. Regardless,
Thank you for adopting the RFC and setting the status to under
discussion from its previous status of "Bike shedding" as I am not
sure if per the process we could discuss the merits of the change -
only the color of the
On 14.08.2014 17:29, Sara Golemon wrote:
> On Thu, Aug 14, 2014 at 2:44 AM, Marc Bennewitz wrote:
>> forgotten the link:
>> https://github.com/php/php-src/pull/658
>>
>>
>> On 14.08.2014 11:43, Marc Bennewitz wrote:
>>>
>>> Hi internals,
>>>
>>> I have created a PR to improve the base 2 and base 1
Hello,
I've opened https://github.com/php/php-src/pull/770 for patches for bugs
#65463, #66036. More details in the PR.
The bug is reproducible on PHP 5.4, 5.5 and 5.6 with and without
--enable-zend-signals.
Please review, I'm hesitant to merge such a core change without more eyes.
Thanks,
Keyu
Dear list,
With her permission, I have taken ownership of Sara's RFC about
multiple default statements in switches. In summary I have:
- Moved RFC from Voting back to Under Discussion
- Made the RFC targets PHP 7 for an E_COMPILE_ERROR, with an
E_DEPRECATED targeted at PHP 5.7.
- Made other mi
On Thu, Aug 14, 2014 at 2:42 PM, Rowan Collins wrote:
> Julien Pauli wrote (on 14/08/2014):
>>
>> It may be possible to interpret the argument, but I think it will need
>>
>> new OPCodes, like ZEND_NEW_WITH_CTOR and ZEND_NEW_WITHOUT_CTOR , and a
>> compiler patch to support those.
>> This may be t
On Thu, Aug 14, 2014 at 2:44 AM, Marc Bennewitz wrote:
> forgotten the link:
> https://github.com/php/php-src/pull/658
>
>
> On 14.08.2014 11:43, Marc Bennewitz wrote:
>>
>> Hi internals,
>>
>> I have created a PR to improve the base 2 and base 10 of the standard
>> math function "log" to reduce r
The PHP development team announces the immediate availability of PHP
5.3.29. This release marks the end of life of the PHP 5.3 series. Future
releases of this series are not planned. All PHP 5.3 users are
encouraged to upgrade to the current stable version of PHP 5.5 or
previous stable version of P
Julien Pauli wrote (on 14/08/2014):
It may be possible to interpret the argument, but I think it will need
new OPCodes, like ZEND_NEW_WITH_CTOR and ZEND_NEW_WITHOUT_CTOR , and a
compiler patch to support those.
This may be thought for PHP7, and I think will benefit from the
ast-compiler RFC if it
On Thu, Aug 14, 2014 at 12:19 PM, Rowan Collins wrote:
> Julien Pauli wrote (on 14/08/2014):
>
>> On Thu, Aug 14, 2014 at 8:26 AM, Tjerk Meesters
>> wrote:
>>>
>>> Hi internals,
>>>
>>> I was sifting through the bucket o’ bugs and found these two related
>>> issues:
>>> https://bugs.php.net/bug.p
Michael Wallner wrote:
> On 14 08 2014, at 11:33, Alain Williams wrote:
>
>> It is OK to define some things as undefined and have them break between
>> releases -
>> even minor releases. I always teach it as undefined - as it is in most
>> programming languages.
>>
>> Likewise, if the next 2 ch
On 14 08 2014, at 11:33, Alain Williams wrote:
> On Thu, Aug 14, 2014 at 10:25:11AM +0100, Chris Wright wrote:
>
>>> My personal opinion is that things like $a[$i++] = $i++ have zero practical
>>> relevance (and also think that anyone using something like this deserves
>>> any breakage he gets)
Julien Pauli wrote (on 14/08/2014):
On Thu, Aug 14, 2014 at 8:26 AM, Tjerk Meesters
wrote:
Hi internals,
I was sifting through the bucket o’ bugs and found these two related issues:
https://bugs.php.net/bug.php?id=67829
https://bugs.php.net/bug.php?id=54162 (closed)
They concern the behaviour
forgotten the link:
https://github.com/php/php-src/pull/658
On 14.08.2014 11:43, Marc Bennewitz wrote:
Hi internals,
I have created a PR to improve the base 2 and base 10 of the standard
math function "log" to reduce rounding errors.
Internally on log(x, 2) the native C function log2(x) and on
Hi internals,
I have created a PR to improve the base 2 and base 10 of the standard
math function "log" to reduce rounding errors.
Internally on log(x, 2) the native C function log2(x) and on log(x, 10)
the native C function log10(x) will be called.
The PR is open since april without any co
On Thu, Aug 14, 2014 at 10:25:11AM +0100, Chris Wright wrote:
> > My personal opinion is that things like $a[$i++] = $i++ have zero practical
> > relevance (and also think that anyone using something like this deserves
> > any breakage he gets). I'd rather save some lines of code than maintain any
On 13 August 2014 20:05, Nikita Popov wrote:
> On Wed, Aug 13, 2014 at 7:18 PM, guilhermebla...@gmail.com <
> guilhermebla...@gmail.com> wrote:
>
>> When is this planned to go through voting process?
>>
>
> Before voting I'd like to have some opinions on the behavioral differences
> the proposal i
On Thu, Aug 14, 2014 at 8:26 AM, Tjerk Meesters
wrote:
> Hi internals,
>
> I was sifting through the bucket o’ bugs and found these two related issues:
> https://bugs.php.net/bug.php?id=67829
> https://bugs.php.net/bug.php?id=54162 (closed)
>
> They concern the behaviour of the engine when a class
28 matches
Mail list logo
