All,
As we’re getting closer to release 5.6.0, and given the very high level of
interest in phpng, I think it’s time for us to provide some clarity
regarding what happens post 5.6.0.
Dmitry and I wrote an RFC proposing that we merge phpng into master and
turn it into the basis of the next maj
See below in red.
> It was not accidental and I said so almost immediately after Andrea sent
> the note to the list about the paragraphs being removed.
>
I didn't see that, my bad. The point I was trying to make is that,
whatever the explanation, I think you should be given the benefit of the
d
hi Zeev,
On Mon, Jul 21, 2014 at 9:31 AM, Zeev Suraski wrote:
> All,
>
>
>
> As we’re getting closer to release 5.6.0, and given the very high level of
> interest in phpng, I think it’s time for us to provide some clarity
> regarding what happens post 5.6.0.
>
>
>
> Dmitry and I wrote an RFC prop
On 21/07/14 08:41, Kris Craig wrote:
>> 1. The vote started with no real case for PHP 7 in there. I made
>> > it clear in past weeks I intended to write one, and said it would take
>> > time. The supposed ‘case for PHP 7’ that was added there by PHP 6
>> > proponents, is now turning out to
On Mon, Jul 21, 2014 at 9:52 AM, Pierre Joye wrote:
> hi Zeev,
>
> On Mon, Jul 21, 2014 at 9:31 AM, Zeev Suraski wrote:
>> All,
>>
>>
>>
>> As we’re getting closer to release 5.6.0, and given the very high level of
>> interest in phpng, I think it’s time for us to provide some clarity
>> regardin
> Hi
>
> We need to consider PHP-Next jump as an opportunity to
> clean our API and finally have something understandable for a newcomer,
> and
> documented. That's a move nobody dared to take in the last decade,
> degrading more and more our codebase in term of understandability and
> flexibility.
Php interactive shell saves commands history when you exit it using 'quit'.
But it throws all you history away when you exit using Ctrl+C. It is common
practice to save history on SIGINT exit (mysql, mongo, etc.)
I would like to implement SIGINT handler for interactive shell to save
history on Ctr
Am 21.07.2014 10:33, schrieb Zeev Suraski:
> Regarding Dmitry saying that phpng is an experimental branch - that was a
> couple of months ago. It evolved, it runs apps in parity with 5.6, and it's
> fine to move it to master right now. The alternative - developing 5.7 on
> master and creating a s
On Mon, Jul 21, 2014 at 7:56 AM, Zeev Suraski wrote:
> The removed paragraphs were actually the RFC’s ‘case for PHP 7’. As the
> champion for the PHP 7 case, I was 100.0% entitled to remove it as I
> thought it wasn’t doing a good job at presenting that case, and replace it
> with some real pro
On 21/07/2014, Zeev Suraski wrote:
> Regarding Dmitry saying that phpng is an experimental branch - that was a
> couple of months ago. It evolved, it runs apps in parity with 5.6, and
> it's
> fine to move it to master right now.
Perhaps you could write a summary of what's changed since phpng w
On 20 Jul 2014 23:32, "Andrea Faulds" wrote:
>
>
> On 20 Jul 2014, at 22:28, Nikita Popov wrote:
>
> > After the vote has been started the RFC was edited by Zeev in order to
strengthen the case for PHP 7. There is nothing wrong with that, adding
additional arguments to an RFC is perfectly fine by
Hi all,
On Mon, Jul 21, 2014 at 6:12 PM, Dmitry Saprykin
wrote:
> Php interactive shell saves commands history when you exit it using 'quit'.
> But it throws all you history away when you exit using Ctrl+C. It is common
> practice to save history on SIGINT exit (mysql, mongo, etc.)
>
> I would l
Hi Julien,
> Hi
>
> I can only agree here.
>
> I'd like a clean API. We need to consider PHP-Next jump as an opportunity
> to
> clean our API and finally have something understandable for a
> newcomer, and documented. That's a move nobody dared to take in the
> last decade, degrading more and mor
Hi Zeev,
On Mon, Jul 21, 2014 at 4:31 PM, Zeev Suraski wrote:
> As we’re getting closer to release 5.6.0, and given the very high level of
> interest in phpng, I think it’s time for us to provide some clarity
> regarding what happens post 5.6.0.
>
Are you willing to have 5.7 branch?
It gives us
On 21 Jul 2014 10:21, "Julien Pauli" wrote:
>
> On Mon, Jul 21, 2014 at 9:52 AM, Pierre Joye wrote:
> > hi Zeev,
> >
> > On Mon, Jul 21, 2014 at 9:31 AM, Zeev Suraski wrote:
> >> All,
> >>
> >>
> >>
> >> As we’re getting closer to release 5.6.0, and given the very high
level of
> >> interest in
Hi all,
On Mon, Jul 21, 2014 at 3:17 PM, Yasuo Ohgaki wrote:
> In old days, crypt() was unusable securely. There are many
> users/developers that
> are used to have static slat. Code like below disables authentication
> completely.
>
> password_hash(hash('sha512', SOME_SECRET_SALT).$password, DE
On 21 Jul 2014 11:24, "Yasuo Ohgaki" wrote:
>
> Hi all,
>
> On Mon, Jul 21, 2014 at 6:12 PM, Dmitry Saprykin <
saprykin.dmi...@gmail.com>
> wrote:
>
> > Php interactive shell saves commands history when you exit it using
'quit'.
> > But it throws all you history away when you exit using Ctrl+C. It
Ok, I will NOT ))
God saves us from bureaucracy
On 21 July 2014 13:46, Michael Wallner wrote:
>
> On 21 Jul 2014 11:24, "Yasuo Ohgaki" wrote:
> >
> > Hi all,
> >
> > On Mon, Jul 21, 2014 at 6:12 PM, Dmitry Saprykin <
> saprykin.dmi...@gmail.com>
> > wrote:
> >
> > > Php interactive shell save
On Mon, 21 Jul 2014, Zeev Suraski wrote:
> As we’re getting closer to release 5.6.0, and given the very high level of
> interest in phpng, I think it’s time for us to provide some clarity
> regarding what happens post 5.6.0.
>
> Dmitry and I wrote an RFC proposing that we merge phpng into master
On 21/07/2014 11:13, Sebastian Bergmann wrote:
> Am 21.07.2014 10:33, schrieb Zeev Suraski:
>> Regarding Dmitry saying that phpng is an experimental branch - that was a
>> couple of months ago. It evolved, it runs apps in parity with 5.6, and it's
>> fine to move it to master right now. The alter
> -Original Message-
> From: Matteo Beccati [mailto:p...@beccati.com]
> Sent: Monday, July 21, 2014 1:08 PM
> To: internals@lists.php.net
> Cc: Sebastian Bergmann
> Subject: Re: [PHP-DEV] RFC: Move phpng to master
>
> To be honest I don't think we're anywhere near the point where it's safe
*From:* yohg...@gmail.com [mailto:yohg...@gmail.com] *On Behalf Of *Yasuo
Ohgaki
*Sent:* Monday, July 21, 2014 12:32 PM
*To:* Zeev Suraski
*Cc:* PHP internals
*Subject:* Re: [PHP-DEV] RFC: Move phpng to master
Hi Zeev,
On Mon, Jul 21, 2014 at 4:31 PM, Zeev Suraski wrote:
As we’re getting cl
On Mon, Jul 21, 2014 at 10:33 AM, Zeev Suraski wrote:
> It's absolutely fine to have separate discussions on cleaning APIs, new
> features and any other changes people think we should do, but it absolutely
> has nothing to do with phpng moving into master. We can take the
> opportunity of a majo
On Mon, Jul 21, 2014 at 11:37 AM, Michael Wallner wrote:
>
> I don't think that a cleanup is nearly as important as php-ng is as we stand
> currently.
>
> The will be no mercy from the competition.
>
> We can start reworking the API when it hit master.
Cleanup reduces the work, not increase it.
On Mon, Jul 21, 2014 at 12:18 PM, Zeev Suraski wrote:
> *From:* yohg...@gmail.com [mailto:yohg...@gmail.com] *On Behalf Of *Yasuo
> Ohgaki
> *Sent:* Monday, July 21, 2014 12:32 PM
> *To:* Zeev Suraski
> *Cc:* PHP internals
> *Subject:* Re: [PHP-DEV] RFC: Move phpng to master
>
>
>
> Hi Zeev,
>
>
Hi Zeev,
On Mon, Jul 21, 2014 at 12:16 PM, Zeev Suraski wrote:
> > -Original Message-
> > From: Matteo Beccati [mailto:p...@beccati.com]
> > Sent: Monday, July 21, 2014 1:08 PM
> > To: internals@lists.php.net
> > Cc: Sebastian Bergmann
> > Subject: Re: [PHP-DEV] RFC: Move phpng to master
On Mon, Jul 21, 2014 at 11:27 AM, Dmitry Stogov wrote:
> Hi Julien,
>
>>
>> Hi
>>
>> I can only agree here.
>>
>> I'd like a clean API. We need to consider PHP-Next jump as an opportunity
>> to
>> clean our API and finally have something understandable for a
>> newcomer, and documented. That's a m
I don't know how things are driven here, but I assume that OSS projects
don't merge stuff into master until tests pass: it's as simple as that.
That's your blocker right there, regardless of voting or any other
discussion going on.
There’s a huge difference between a major code changes as we li
On Mon, Jul 21, 2014 at 12:24 PM, Ferenc Kovacs wrote:
>
> He just asks if we will have a 5.7 release while working on the next major
> in master.
> I don't think that we can release the php-next under a years, so I think
> that an 5.7 could be warranted (to keep up with our roadmap), but depends
He just asks if we will have a 5.7 release while working on the next major
in master.
I don't think that we can release the php-next under a years, so I think
that an 5.7 could be warranted (to keep up with our roadmap), but depends
on wether or not we have enough new (BC-safe) features.
I don’t
On Mon, Jul 21, 2014 at 12:30 PM, Zeev Suraski wrote:
>
> There’s a huge difference between a major code changes as we line up for a
> new major version – one that requires widespread testing and community
> support – and the relatively minor changes we’ve had here ever since PHP 5.
>
> So from m
On Mon, 21 Jul 2014, Dmitry Stogov wrote:
> > I can only agree here.
> >
> > I'd like a clean API. We need to consider PHP-Next jump as an
> > opportunity to clean our API and finally have something
> > understandable for a newcomer, and documented. That's a move nobody
> > dared to take in the
On Mon, Jul 21, 2014 at 12:31 PM, Zeev Suraski wrote:
> He just asks if we will have a 5.7 release while working on the next major
> in master.
>
> I don't think that we can release the php-next under a years, so I think
> that an 5.7 could be warranted (to keep up with our roadmap), but depends
>
Hi Matteo,
We have very limited forces to test everything. Once we we have bug reports
we may look into the problems and fix them.
According to FAST_ZPP part, the commit message and comments in the code
clearly say that this part may be changed in the future.
We should vote for it separately and
On Mon, Jul 21, 2014 at 12:41 PM, Derick Rethans wrote:
> On Mon, 21 Jul 2014, Dmitry Stogov wrote:
>
>> > I can only agree here.
>> >
>> > I'd like a clean API. We need to consider PHP-Next jump as an
>> > opportunity to clean our API and finally have something
>> > understandable for a newcomer,
On Mon, Jul 21, 2014 at 12:41 PM, Dmitry Stogov wrote:
> Hi Matteo,
>
> We have very limited forces to test everything. Once we we have bug reports
> we may look into the problems and fix them.
>
> According to FAST_ZPP part, the commit message and comments in the code
> clearly say that this part
On Mon, Jul 21, 2014 at 2:24 PM, Julien Pauli wrote:
> On Mon, Jul 21, 2014 at 11:27 AM, Dmitry Stogov wrote:
> > Hi Julien,
> >
> >>
> >> Hi
> >>
> >> I can only agree here.
> >>
> >> I'd like a clean API. We need to consider PHP-Next jump as an
> opportunity
> >> to
> >> clean our API and fina
On Mon, Jul 21, 2014 at 11:50 AM, Dmitry Saprykin
wrote:
> Ok, I will NOT ))
> God saves us from bureaucracy
Well, Michael's view is known.
However let me explain what RFCs bring, besides bureaucracy.
- clear identification of use cases, incl. edge cases
- better design and design reviews
- doc
On Mon, Jul 21, 2014 at 12:50 PM, Dmitry Stogov wrote:
> We thought about it many time, but didn't have time to do it.
cleanup makes code bases smaller, more maintainable, easier to change.
The time spent to port dead parts of PHP should have been better
spent. It is too late to do that :)
--
On Mon, Jul 21, 2014 at 12:31 PM, Zeev Suraski wrote:
>
>
> He just asks if we will have a 5.7 release while working on the next major
> in master.
>
> I don't think that we can release the php-next under a years, so I think
> that an 5.7 could be warranted (to keep up with our roadmap), but depe
On Mon, Jul 21, 2014 at 9:31 AM, Zeev Suraski wrote:
> All,
>
> As we’re getting closer to release 5.6.0, and given the very high level of
> interest in phpng, I think it’s time for us to provide some clarity
> regarding what happens post 5.6.0.
>
> Dmitry and I wrote an RFC proposing that we mer
On Mon, Jul 21, 2014 at 1:01 PM, Ferenc Kovacs wrote:
> On Mon, Jul 21, 2014 at 12:31 PM, Zeev Suraski wrote:
>
>>
>>
>> He just asks if we will have a 5.7 release while working on the next major
>> in master.
>>
>> I don't think that we can release the php-next under a years, so I think
>> that
On Mon, Jul 21, 2014 at 1:10 PM, Nikita Popov wrote:
> On Mon, Jul 21, 2014 at 9:31 AM, Zeev Suraski wrote:
>
> > All,
> >
> > As we’re getting closer to release 5.6.0, and given the very high level
> of
> > interest in phpng, I think it’s time for us to provide some clarity
> > regarding what h
On Mon, Jul 21, 2014 at 1:10 PM, Nikita Popov wrote:
> There are actually two questions here:
> 1. Do we want to base the next major version on phpng?
> 2. Do we want to merge phpng into master?
As of now, I am against both. But as I said earlier I am open as long
as the minimal requirements are
Hi Yasuo,
Some times ago I mailed my idea about refactoring random number
generator API with min BC breaks but I didn't create an RFC right now.
see http://marc.info/?l=php-internals&m=137772363015217
Marc
On 16.07.2014 07:13, Yasuo Ohgaki wrote:
Hi all,
There are few places that uses php_
On 21 ביול 2014, at 14:20, Ferenc Kovacs wrote:
> On Mon, Jul 21, 2014 at 1:10 PM, Nikita Popov wrote:
> On Mon, Jul 21, 2014 at 9:31 AM, Zeev Suraski wrote:
>
> > All,
> >
> > As we’re getting closer to release 5.6.0, and given the very high level of
> > interest in phpng, I think it’s time f
Am 21.7.2014 um 12:52 schrieb Pierre Joye :
> On Mon, Jul 21, 2014 at 11:50 AM, Dmitry Saprykin
> wrote:
>> Ok, I will NOT ))
>> God saves us from bureaucracy
>
> Well, Michael's view is known.
>
> However let me explain what RFCs bring, besides bureaucracy.
>
> - clear identification of use ca
On 21 Jul 2014, at 12:10, Nikita Popov wrote:
> The latter is tied to the question whether or not we want to have a PHP 5.7
> release in the meantime. I'm not really sure whether or not that would be
> good, I would recommend opening a separate thread about that question.
The way I see it, we s
> -Original Message-
> From: Andrea Faulds [mailto:a...@ajf.me]
> Sent: Monday, July 21, 2014 3:55 PM
> To: Nikita Popov
> Cc: Zeev Suraski; PHP internals
> Subject: Re: [PHP-DEV] RFC: Move phpng to master
>
>
> I think we should have a PHP 5.7. There are plenty of things we can
still do in
Thank you for clarification. I'm agree with all points. But I think in this
particular case (1 file, <20 lines of code) simple review could be enough.
I'm new in php development and may be I am missing some workflow steps. If
RFC is absolutely necessary I will be happy to create it but I have no
en
On 21 Jul 2014, at 14:06, Zeev Suraski wrote:
> I'm not sure where the 2-3 years is coming from, but again, I see no
> reason why we wouldn't be able to push .NEXT out within a year (if it's
> just phpng along then actually a lot less, but I'm allowing time for extra
> features we may want to pu
On Mon, Jul 21, 2014 at 3:06 PM, Zeev Suraski wrote:
> I'm not sure where the 2-3 years is coming from, but again, I see no
> reason why we wouldn't be able to push .NEXT out within a year (if it's
> just phpng along then actually a lot less, but I'm allowing time for extra
> features we may want
> -Original Message-
> From: Andrea Faulds [mailto:a...@ajf.me]
> Sent: Monday, July 21, 2014 4:10 PM
> To: Zeev Suraski
> Cc: Nikita Popov; PHP internals
> Subject: Re: [PHP-DEV] RFC: Move phpng to master
>
>
> We *could* make PHP NEXT in a year, sure, but it won't be worthwhile
being
> ca
On 21 Jul 2014, at 14:47, Zeev Suraski wrote:
> Everything I know about the PHP community, combined with the amazing level
> of interest that the recent PHPNG benchmarks garnered, tells me that it
> wrong.
> People would love to get it even if it was just the performance & memory
> footprint gai
On Mon, 2014-07-21 at 13:12 +0400, Dmitry Saprykin wrote:
> Php interactive shell saves commands history when you exit it using 'quit'.
> But it throws all you history away when you exit using Ctrl+C. It is common
> practice to save history on SIGINT exit (mysql, mongo, etc.)
>
> I would like to i
On Mon, Jul 21, 2014 at 3:47 PM, Zeev Suraski wrote:
d PHP NEXT.
>
> Everything I know about the PHP community, combined with the amazing level
> of interest that the recent PHPNG benchmarks garnered, tells me that it
> wrong.
You needed one year+ to stabilize opcache, how long will you need for
On 21/07/2014 12:41, Dmitry Stogov wrote:
> Hi Matteo,
>
> We have very limited forces to test everything. Once we we have bug reports
> we may look into the problems and fix them.
I've been trying to help with testing and reporting on IRC the results.
I think I've mentioned Doctrine a few times
On Mon, 21 Jul 2014, Zeev Suraski wrote:
> From: Andrea Faulds [mailto:a...@ajf.me]
> >
> > We *could* make PHP NEXT in a year, sure, but it won't be worthwhile
> > being called PHP NEXT.
>
> Everything I know about the PHP community, combined with the amazing
> level of interest that the recen
changed "write_history" at the end to "append_history" after
each cli_is_valid_code.
Now it is -1 line, +1 line commit and completely looks like bug fix. )
On 21 July 2014 18:00, Johannes Schlüter wrote:
> On Mon, 2014-07-21 at 13:12 +0400, Dmitry Saprykin wrote:
> > Php interactive shell saves
On Mon, Jul 21, 2014 at 12:41 PM, Dmitry Stogov wrote:
> Hi Matteo,
>
> We have very limited forces to test everything. Once we we have bug reports
> we may look into the problems and fix them.
>
Wouldn't it be super easy to use the HHVM team infrastructure to test a
version against various PHP
On Mon, Jul 21, 2014 at 4:19 PM, Benjamin Eberlei wrote:
> On Mon, Jul 21, 2014 at 12:41 PM, Dmitry Stogov wrote:
>
>> Hi Matteo,
>>
>> We have very limited forces to test everything. Once we we have bug reports
>> we may look into the problems and fix them.
>>
>
> Wouldn't it be super easy to us
Yasuo,
> E_NOTICE for password larger than 72 is mandatory. Current password_hash()
> works without any sign of problem even if it may not be working as
> authentication.
> I'll add E_NOTICE as bug fix if there aren't any more comments.
Could you please not.
I have asked you to draft an RFC to j
Hey：
> 在 2014年7月21日，18:56，Pierre Joye 写道：
>
>> On Mon, Jul 21, 2014 at 12:50 PM, Dmitry Stogov wrote:
>>
>> We thought about it many time, but didn't have time to do it.
>
> cleanup makes code bases smaller, more maintainable, easier to change.
> The time spent to port dead parts of PHP should h
Hey:
> 在 2014年7月21日，19:02，Ferenc Kovacs 写道：
>
>> On Mon, Jul 21, 2014 at 12:31 PM, Zeev Suraski wrote:
>>
>>
>>
>> He just asks if we will have a 5.7 release while working on the next major
>> in master.
>>
>> I don't think that we can release the php-next under a years, so I think
>> that an 5.
On Mon, Jul 21, 2014 at 5:36 PM, Xinchen Hui wrote:
>
>
> 发自我的 iPad
>
> 在 2014年7月21日，23:30，Pierre Joye 写道：
>
>
> On Jul 21, 2014 5:28 PM, "Xinchen Hui" wrote:
>
>> Or you suggest we stop the current work to waiting them come their self?
>
> This is exactly what you have done. So what?
>
> But no
On Mon, Jul 21, 2014 at 5:28 PM, Xinchen Hui wrote:
> Hey:
>
> > 在 2014年7月21日，19:02，Ferenc Kovacs 写道：
> >
> >> On Mon, Jul 21, 2014 at 12:31 PM, Zeev Suraski wrote:
> >>
> >>
> >>
> >> He just asks if we will have a 5.7 release while working on the next
> major
> >> in master.
> >>
> >> I don't
Am 2.7.2014 um 15:43 schrieb Dmitry Stogov :
> I don't have good ideas out of the box and I probably won't be able to look
> into this before next week.
Hey, I still have no real idea how to solve it without breaking opcache.
This one seems to be considered like a blocking bug for 5.6.
Could yo
Hey:
I really don't like arguing in english, so this will be my last
reply in this thread.
On Tue, Jul 22, 2014 at 12:10 AM, Ferenc Kovacs wrote:
>
>
>
> On Mon, Jul 21, 2014 at 5:28 PM, Xinchen Hui wrote:
>>
>> Hey:
>>
>> > 在 2014年7月21日，19:02，Ferenc Kovacs 写道：
>> >
>> >> On Mon, Jul 21,
hi,
On Tue, Jul 22, 2014 at 3:42 AM, Xinchen Hui wrote:
>> https://wiki.php.net/rfc/uniform_variable_syntax
>> https://wiki.php.net/rfc/size_t_and_int64_next
>
> aren't they discussed and voted? what do you mean by we can't even
> start in previous comment?
The int64 yes, that means and it is
Hi Anthony,
On Mon, Jul 21, 2014 at 11:32 PM, Anthony Ferrara
wrote:
> > E_NOTICE for password larger than 72 is mandatory. Current
> password_hash()
> > works without any sign of problem even if it may not be working as
> > authentication.
> > I'll add E_NOTICE as bug fix if there aren't any mo
Hi Yasuo,
On Tue, Jul 22, 2014 at 5:00 AM, Yasuo Ohgaki wrote:
> Hi Anthony,
>
> On Mon, Jul 21, 2014 at 11:32 PM, Anthony Ferrara
> wrote:
>
>> > E_NOTICE for password larger than 72 is mandatory. Current
>> password_hash()
>> > works without any sign of problem even if it may not be working as
Hi Zeev,
On Mon, Jul 21, 2014 at 7:18 PM, Zeev Suraski wrote:
> Hi Zeev,
>
>
>
> On Mon, Jul 21, 2014 at 4:31 PM, Zeev Suraski wrote:
>
> As we’re getting closer to release 5.6.0, and given the very high level of
> interest in phpng, I think it’s time for us to provide some clarity
> regarding
On 2014-07-21, Michael Wallner wrote:
> --001a11345984e013cd04feb0d9a1
> Content-Type: text/plain; charset=UTF-8
> Content-Transfer-Encoding: quoted-printable
>
> On 21 Jul 2014 10:21, "Julien Pauli" wrote:
> PHP-Next.
>
> I don't think that a cleanup is nearly as important as php-ng is as we
> s
Hi David,
On Tue, Jul 22, 2014 at 2:08 PM, David Soria Parra wrote:
> On 2014-07-21, Michael Wallner wrote:
> > --001a11345984e013cd04feb0d9a1
> > Content-Type: text/plain; charset=UTF-8
> > Content-Transfer-Encoding: quoted-printable
> >
> > On 21 Jul 2014 10:21, "Julien Pauli" wrote:
> > PHP
Am 7/21/14, 10:21 PM, schrieb Yasuo Ohgaki:
>
> Even if we have PHP-5.7 branch, we have merge up policy. Therefore,
> any new feature will end up with master, I suppose. If a new feature is
> only available to PHP-5.7 branch, it's a merge bug, isn't it?
>
> Regards,
We had this policy before
On Mon, Jul 21, 2014 at 2:21 AM, Michael Wallner wrote:
> On 20 Jul 2014 23:32, "Andrea Faulds" wrote:
> >
> >
> > On 20 Jul 2014, at 22:28, Nikita Popov wrote:
> >
> > > After the vote has been started the RFC was edited by Zeev in order to
> strengthen the case for PHP 7. There is nothing wro
Hi Bob,
Now I think it's not fixable by design :(
I'll try to think about it later today.
Could you please collect all related issues.
Thanks. Dmitry.
On Mon, Jul 21, 2014 at 8:36 PM, Bob Weinand wrote:
> Am 2.7.2014 um 15:43 schrieb Dmitry Stogov :
>
> I don't have good ideas out of the box
Pierre,
I don't replay to you, because it's bad for my health. Many people here
would agree with me.
I prefer to do things instead of endlessly repeated words.
According to PHPNG - we set one big goal (performance), and worked on it
really hard. Now everyone may see the result. It's just not poss
78 matches
Mail list logo
