> -Original Message-
> From: morrison.l...@gmail.com [mailto:morrison.l...@gmail.com] On
> Behalf Of Levi Morrison
> Sent: Friday, December 12, 2014 10:00 PM
> To: Zeev Suraski
> Cc: Julien Pauli; PHP Internals
> Subject: Re: [PHP-DEV] On the road to PHP 5.7 , or not ?
>
> >> - If we go for
> On 2 Dec 2014, at 21:44, Andrea Faulds wrote:
>
> Good evening once again,
>
> I’m putting the ZPP Failure on Overflow RFC to a vote. This RFC is an
> important prerequisite to the Big Integer Support RFC, as it ensures safety
> in implicit integer parameter conversions.
>
> The RFC requir
On 12 December 2014 at 23:00, Andrea Faulds wrote:
>
> I must disagree: 5.7 would only be trivially different from 5.6
> (deprecations), the effort involved is only as much as continuing to maintain
> 5.6, and we have to do that anyway. So there’s no problem with working on
> both.
>
I have to
Hi!
> On 12 Dec 2014, at 19:40, Zeev Suraski wrote:
>
>> If not : we'll happen having 3 active versions (5.6 , 5.7 and 7.0) and one
>> sec-
>> fix only (5.5) , *this is something we don't want* , because we have the
>> feeling that it is too much pain to maintain so many versions alive.
>
> It'
>> - If we go for 5.7 :
>> We could release it this summer (2015) , but that would mean that 7.0
>> wouldn't come before summer 2016.
>> Releasing a 5.7 will lean the release cycle curve, but it is not
>> mandatory, that
>> should be debatted.
>
> A 5.7 that pushes 7.0 into Summer 2016 is IMHO a st
> So the main question is : *What version will we release next year ?*
We've already answered that question, as per the PHP 7 timeline RFC, we're
aiming to release PHP 7 in 2015. Sure, given the aggressive timeline
there's the possibility that we won't be able to make it on time, but that's
our g
On 12 December 2014 at 10:07, Levi Morrison wrote:
> Just because we are releasing PHP 7.0 next year (well, according to
> our timeline anyway) that doesn't mean we can't release a 5.7.
Agreed.
I have to apologise here — I've had a draft RFC half-written for over
a week at this point that would
On Dec 10, 2014, at 11:24 PM, Stanislav Malyshev wrote:
>> the real-world code I've seen, it is the least confusing. (I'll see
>
> Which real-world code you are talking about? Examples please.
I'm having trouble digging any up -- FB's codebase has >10k occurrences of this
feature and I have ye
Just because we are releasing PHP 7.0 next year (well, according to
our timeline anyway) that doesn't mean we can't release a 5.7.
The advantage of PHP 5.7 is clear to me at least: it would extend
support for the 5.X series by another year, get bug fixes, and contain
E_DEPRECATED warnings and othe
On Dec 12, 2014 9:34 PM, "Derick Rethans" wrote:
>
> On Fri, 12 Dec 2014, Julien Pauli wrote:
>
> > So the main question is : *What version will we release next year ?*
> >
> > Will we have a PHP 5.7, or jump directly to a 7.0 ?
> >
> > Don't forget, that if we go for a 5.7 , then we won't have a
On Fri, Dec 12, 2014 at 3:47 PM, Ferenc Kovacs wrote:
>
>
> On Fri, Dec 12, 2014 at 3:34 PM, Derick Rethans wrote:
>>
>> On Fri, 12 Dec 2014, Julien Pauli wrote:
>>
>> > So the main question is : *What version will we release next year ?*
>> >
>> > Will we have a PHP 5.7, or jump directly to a 7
Hi,
On Fri, Dec 12, 2014 at 5:35 PM, guilhermebla...@gmail.com <
guilhermebla...@gmail.com> wrote:
>
> RFC is updated exposing both possible usages with both explanations.
> Hope it doesn't confuse even more.
>
>
Perfect! Thanks.
Cheers,
--
Florian Margaine
RFC is updated exposing both possible usages with both explanations.
Hope it doesn't confuse even more.
On Fri, Dec 12, 2014 at 11:30 AM, Florian Margaine
wrote:
>
> Hi,
>
> Le 12 déc. 2014 17:28, "guilhermebla...@gmail.com" <
> guilhermebla...@gmail.com> a écrit :
> >
> > It's part of the histor
Hi Christian
2014-12-12 15:39 GMT+01:00 Christian Stoller :
> It works again ;)
Good it is fixed for now, and if you have any future issues you can
use the webmaster list for any such issues:
php-webmas...@lists.php.net
--
regards,
Kalle Sommer Nielsen
ka...@php.net
--
PHP Internals - PHP
Hi,
Le 12 déc. 2014 17:28, "guilhermebla...@gmail.com" <
guilhermebla...@gmail.com> a écrit :
>
> It's part of the history of that RFC, accessible here:
https://wiki.php.net/rfc/abstract_final_class?rev=1417060830
>
But then it isn't clear as of right now. What is proposed? The example? The
votes
It's part of the history of that RFC, accessible here:
https://wiki.php.net/rfc/abstract_final_class?rev=1417060830
On Fri, Dec 12, 2014 at 11:18 AM, Florian Margaine
wrote:
>
> Hi,
>
>
>
> On Fri, Dec 12, 2014 at 5:12 PM, guilhermebla...@gmail.com <
> guilhermebla...@gmail.com> wrote:
>>
>> Hi i
Hi,
On Fri, Dec 12, 2014 at 5:12 PM, guilhermebla...@gmail.com <
guilhermebla...@gmail.com> wrote:
>
> Hi internals,
>
> After a good round of discussion, I updated the original "abstract final
> class" proposal into a "static class" proposal.
> However, I kept both patches online so it's up to
Hi Thomas,
> On 12 Dec 2014, at 15:42, Thomas Bley wrote:
>
> 1) I think it would be better to have ObjectSafe Calls, e.g.
>
> class User {
> ...
> public function delete() {
>// delete ...
> }
> }
> class Users {
> public function find($id) {
>if ($this->db->query(...)) return new
Hi internals,
After a good round of discussion, I updated the original "abstract final
class" proposal into a "static class" proposal.
However, I kept both patches online so it's up to voters decide which one
it could be implemented.
Patches are now complete and voting phase starts now and will be
Hello Josh,
1) I think it would be better to have ObjectSafe Calls, e.g.
class User {
...
public function delete() {
// delete ...
}
}
class Users {
public function find($id) {
if ($this->db->query(...)) return new User($id);
return 'not found';
}
}
$users = new Users();
$r
On Fri, Dec 12, 2014 at 3:34 PM, Derick Rethans wrote:
>
> On Fri, 12 Dec 2014, Julien Pauli wrote:
>
> > So the main question is : *What version will we release next year ?*
> >
> > Will we have a PHP 5.7, or jump directly to a 7.0 ?
> >
> > Don't forget, that if we go for a 5.7 , then we won't h
W dniu 2014-12-12 13:01, Christian Stoller pisze:
> Hi.
>
> When I am on the page http://php.net/manual/en/book.intl.php and click on
> “UConverter - The UConverter class”, I get linked to a blank page
> (http://php.net/manual/en/class.uconverter.php).
>
> Same for http://php.net/mailing-lists.p
On Fri, 12 Dec 2014, Julien Pauli wrote:
> So the main question is : *What version will we release next year ?*
>
> Will we have a PHP 5.7, or jump directly to a 7.0 ?
>
> Don't forget, that if we go for a 5.7 , then we won't have a 7.0 at
> least one year later.
We have accepted the timeline
On Fri, Dec 12, 2014 at 2:45 PM, Julien Pauli wrote:
>
> Hi people.
>
> Ferenc and I, actual RM of 5.5 and 5.6 , were discussing the calendar today
> on IRC.
>
> Let's start with facts :
>
> - We release new PHP versions (major or minor) on summer. Usually, if we
> can have it end of June, it is g
On 12 December 2014 at 13:45, Julien Pauli wrote:
>
> - If we go for 7.0 :
> I wouldn't mind delaying its release to November(2015) if needed, its a
> major, extra care should be taken. However, not later : our release process
> status for 2 years of active life , if 7.0 were to be released in 201
Hi people.
Ferenc and I, actual RM of 5.5 and 5.6 , were discussing the calendar today
on IRC.
Let's start with facts :
- We release new PHP versions (major or minor) on summer. Usually, if we
can have it end of June, it is good.
- We may delay that, 5.6 got released end of summer : in september
On Fri, Dec 12, 2014 at 1:21 PM, Jan Ehrhardt wrote:
>
> Michael Wallner in php.internals (Fri, 12 Dec 2014 12:02:53 +0100):
> >On 11/12/14 09:36, Ferenc Kovacs wrote:
> >
> >> CCing Mike as he was the author who originally added 3.0 to the exclude
> >> list.
> >
> >Yes, I'm on ArchLinux, which ha
Michael Wallner in php.internals (Fri, 12 Dec 2014 12:02:53 +0100):
>On 11/12/14 09:36, Ferenc Kovacs wrote:
>
>> CCing Mike as he was the author who originally added 3.0 to the exclude
>> list.
>
>Yes, I'm on ArchLinux, which has very recent software versions, so I
>just added it to the exclude, w
Am 12.12.2014 um 09:47 schrieb Julien Pauli:
> In the worst scenario, there is also: downgrade your Bison.
I have done that for now, of course. What worries me is the reliance
on outdated and unsupported tools.
--
PHP Internals - PHP Runtime Development Mailing List
To unsubscribe, visit: http
Hi,
both locations are fine for me. Which mirror do you use?
Cheers,
maciej.stol...@leonex.de
W dniu 2014-12-12 13:01, Christian Stoller pisze:
Hi.
When I am on the page http://php.net/manual/en/book.intl.php and click on
“UConverter - The UConverter class”, I get linked to a blank page
(ht
Hi.
When I am on the page http://php.net/manual/en/book.intl.php and click on
“UConverter - The UConverter class”, I get linked to a blank page
(http://php.net/manual/en/class.uconverter.php).
Same for http://php.net/mailing-lists.php
Something seems to be broken there.
Christian
P.S. Sorry
On 11/12/14 09:36, Ferenc Kovacs wrote:
> CCing Mike as he was the author who originally added 3.0 to the exclude
> list.
Yes, I'm on ArchLinux, which has very recent software versions, so I
just added it to the exclude, when I upgraded bison to 3.0 and then
downgraded bison again.
IIRC ZTS buil
I agree, doing lots of if statements gets bloated. Someone would only
use this method if they was comfortable with it either returning null or
the desired result.
On 11/12/2014 16:00, Rowan Collins wrote:
guilhermebla...@gmail.com wrote on 11/12/2014 15:57:
Not trying to demerit the proposal,
On Thu, Dec 11, 2014 at 2:36 PM, Leigh wrote:
> On 11 December 2014 at 07:52, Sebastian Bergmann wrote:
>> Hi!
>>
>> I just updated my notebook to Fedora 21 and am no longer able to
>> build PHP on it since I now have bison 3.0.2 instead of bison 2.7.
>>
>> bison 3.0 is blacklisted in Zend/ac
34 matches
Mail list logo
