On Fri, Dec 26, 2014 at 8:33 AM, Michael Wallner m...@php.net wrote:
There's already ZEND_RESULT_CODE, or did I miss anything?
Yes, to read the thread :)
We are not talking about the lack of a status typedef but about the
inconsistencies across PHP internal APIs. And what Xinchen suggests
below
hidden in some random old threads. Thanks :)
--
Pierre
@pierrejoye | http://www.libgd.org
--
PHP Internals - PHP Runtime Development Mailing List
To unsubscribe, visit: http://www.php.net/unsub.php
hi,
On Wed, Dec 24, 2014 at 7:37 PM, Yasuo Ohgaki yohg...@ohgaki.net wrote:
Hi Pierre,
On Wed, Dec 24, 2014 at 4:23 PM, Pierre Joye pierre@gmail.com wrote:
Please keep in mind that this problem is:
. not json specific
. not specific at runtime but could also happen before a script get
On Wed, Dec 24, 2014 at 7:53 PM, Xinchen Hui larue...@php.net wrote:
On Wed, Dec 24, 2014 at 3:57 PM, Pierre Joye pierre@gmail.com wrote:
On Dec 24, 2014 2:38 PM, Stanislav Malyshev smalys...@gmail.com wrote:
Hi!
But: return 0 and return FAILURE... which is simpler?
It's equally
On Dec 24, 2014 8:41 PM, Johannes Schlüter johan...@schlueters.de wrote:
On Wed, 2014-12-24 at 05:06 +, Andrea Faulds wrote:
typedef enum _zend_success {
FAILURE = 0,
SUCCESS = 1
} zend_success;
mysqlnd uses a enum for that already. See
On Dec 25, 2014 1:13 AM, Levi Morrison le...@php.net wrote:
On Wed, Dec 24, 2014 at 10:34 AM, Andrea Faulds a...@ajf.me wrote:
On 24 Dec 2014, at 17:22, Levi Morrison le...@php.net wrote:
Hmm. This thread doesn't seem to mention it, but why must failure be
negative? I understand the
with unify the APIs.
Cheers,
--
Pierre
@pierrejoye | http://www.libgd.org
--
PHP Internals - PHP Runtime Development Mailing List
To unsubscribe, visit: http://www.php.net/unsub.php
use if (foo() 0) to check for errors. That’s
the point of making FAILURE be -1, AIUI. It makes it consistent with other
things, like fork() or strpos().
Thanks.
lets make this simple.
first we need unify PHP self..
Exactly, and it is not like we can unify libc ourselves ;)
--
Pierre
Hi François,
On Thu, Dec 25, 2014 at 2:40 PM, François Laupretre
franc...@tekwire.net wrote:
De : Pierre Joye [mailto:pierre@gmail.com]
Anyone dying while waiting to see PHP having case sensitive symbols
handling should go ahead with a RFC.
For those interested, I just created a PR
matter, or CS matter. Not a
bug, by no mean.
Cheers,
--
Pierre
@pierrejoye | http://www.libgd.org
--
PHP Internals - PHP Runtime Development Mailing List
To unsubscribe, visit: http://www.php.net/unsub.php
This issue has been reported earlier on secur...@php.net and is being
discussed and analyzed. It is not a simple task.
I have to thank the reporter to have it done the right way.
Maybe Lukas can learn from them for his next report.
Cheers,
Pierre
On Dec 23, 2014 11:20 PM, Scott Arciszewski
On Dec 24, 2014 3:17 AM, Andrea Faulds a...@ajf.me wrote:
On 23 Dec 2014, at 20:12, Yasuo Ohgaki yohg...@ohgaki.net wrote:
Hi,
On Wed, Dec 24, 2014 at 4:51 AM, Pierre Joye pierre@gmail.com
wrote:
This issue has been reported earlier on secur...@php.net and is being
discussed
();
Or something along this line.
Yes, it will mean yet another large set of changes for ext developers. But
at this point, it may be a good time to do it.
Cheers,
Pierre
On Dec 22, 2014 4:33 PM, F N Laupretre nf.laupre...@yahoo.fr wrote:
With all due respect, I don't like the idea that you know better than me
what's important or not.
I should put the I am not saying .. outlined. Also no matter how we look
at it, there are actually a good amount of things that
?
These are all things we should take into account, not only heh, let
make symbols case sensitive.
Cheers,
--
Pierre
@pierrejoye | http://www.libgd.org
--
PHP Internals - PHP Runtime Development Mailing List
To unsubscribe, visit: http://www.php.net/unsub.php
On Mon, Dec 22, 2014 at 3:05 PM, Mike Dugan m...@mjdugan.com wrote:
Development should also be a consideration, I see a lot of developers using
Windows for local development (even on the irc channels). These are the same
ones who are, in my experience, less likely to be aware of solutions
On Dec 22, 2014 12:27 PM, Ralf Lang l...@b1-systems.de wrote:
On 21.12.2014 16:12, Alain Williams wrote:
On Sun, Dec 21, 2014 at 05:23:53PM +0300, Alexey Zakhlestin wrote:
did you hear about RHSCL?
http://developerblog.redhat.com/2014/06/04/red-hat-software-collections-rhscl-1-1-now-ga/
, based on coding
standard. But for internals names, it is going to be a major pain.
Cheers,
Pierre
--
PHP Internals - PHP Runtime Development Mailing List
To unsubscribe, visit: http://www.php.net/unsub.php
On Dec 21, 2014 10:50 AM, Xinchen Hui larue...@php.net wrote:
Hey:
On Sun, Dec 21, 2014 at 11:43 AM, Pierre Joye pierre@gmail.com
wrote:
On Dec 21, 2014 10:23 AM, Xinchen Hui larue...@php.net wrote:
Hey:
I am strongly against to remove ext/mysql
that means, all wordpress
Hi,
Quick head up in case you missed it:
Update your git client asap
https://github.com/blog/1938-git-client-vulnerability-announced
Cheers,
Pierre
On Dec 17, 2014 5:26 PM, Michael Wallner m...@php.net wrote:
On 19/08/14 09:49, Michael Wallner wrote:
Hi PHP internals!
I've created an RFC for discussion:
Whether it is feasible to add pecl_http v2 to the core.
https://wiki.php.net/rfc/pecl_http
Just a minor update: the
On Dec 16, 2014 9:10 PM, Zeev Suraski z...@zend.com wrote:
-Original Message-
From: Andrea Faulds [mailto:a...@ajf.me]
Sent: Tuesday, December 16, 2014 10:00 AM
To: Ferenc Kovacs
Cc: Matteo Beccati; Xinchen Hui; PHP Internals
Subject: Re: [PHP-DEV] [RFC] PHP 5.7
Hey,
On Dec 16, 2014 10:23 PM, Zeev Suraski z...@zend.com wrote:
-Original Message-
From: morrison.l...@gmail.com [mailto:morrison.l...@gmail.com] On
Behalf Of Levi Morrison
Sent: Tuesday, December 16, 2014 9:29 AM
To: Xinchen Hui
Cc: Andrea Faulds; PHP Internals
Subject: Re:
On Dec 17, 2014 4:19 AM, Andrea Faulds a...@ajf.me wrote:
Hey Florian,
On 16 Dec 2014, at 19:55, Florian Margaine flor...@margaine.com wrote:
Hi list,
I think having a minor PHP version for the only sake of adding
E_DEPRECATED
is kind of pointless to be honest. Historically, PHP (or
On Wed, Dec 17, 2014 at 10:45 AM, Andrea Faulds a...@ajf.me wrote:
Hi Pierre,
On 16 Dec 2014, at 23:42, Pierre Joye pierre@gmail.com wrote:
On Dec 17, 2014 4:19 AM, Andrea Faulds a...@ajf.me wrote:
Hmm, actually, a 2to3-esque tool and a formal extension of 5.6's support
by a year
On Dec 15, 2014 11:53 PM, Derick Rethans der...@php.net wrote:
On Sat, 13 Dec 2014, Pierre Joye wrote:
On Dec 12, 2014 9:34 PM, Derick Rethans der...@php.net wrote:
On Fri, 12 Dec 2014, Julien Pauli wrote:
So the main question is : *What version will we release next year
On Dec 13, 2014 2:19 PM, Zeev Suraski z...@zend.com wrote:
Levi, Andrea, Adam, and others that suggested we can do 5.7 in parallel
while sticking to the 7.0 timeline:
1. I was replying to Julien. Julien said in at least 3 different places
in
his email that if we do 5.7, we'll clearly not
On Dec 12, 2014 9:34 PM, Derick Rethans der...@php.net 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
APIs change between x.y and x.y+1, we do
allow them.
However I worry much more about what we do (not) for userland and some
bigger changes internally, those that will be very hard to sell for
7.x.
Expanding the scope of this too much will end up as failure.
--
Pierre
@pierrejoye | http
the rest of mcrypt.
For the record, when I applied these changes I did not want to create
new APIs only for Windows. The key point is to have portability first
for the existing functions.
--
Pierre
@pierrejoye | http://www.libgd.org
--
PHP Internals - PHP Runtime Development Mailing List
serious flaws will be found in
libmcrypt and never get fixed.
Cheers,
--
Pierre
@pierrejoye | http://www.libgd.org
--
PHP Internals - PHP Runtime Development Mailing List
To unsubscribe, visit: http://www.php.net/unsub.php
not need changing?
I suppose you mean to replace the functions implementation to use
openssl + some custom codes? As maintaining our own library is not
going to be a good idea :)
--
Pierre
@pierrejoye | http://www.libgd.org
--
PHP Internals - PHP Runtime Development Mailing List
To unsubscribe
move. Maybe add a vote
option to either keep the placebo (less code change) or remove it
(easier in the long term, no more TS build break, or fewer).
Cheers,
--
Pierre
@pierrejoye | http://www.libgd.org
--
PHP Internals - PHP Runtime Development Mailing List
To unsubscribe, visit: http
I am not even sure there is one in CLI.
--
Pierre
@pierrejoye | http://www.libgd.org
--
PHP Internals - PHP Runtime Development Mailing List
To unsubscribe, visit: http://www.php.net/unsub.php
finish a new feature may not be
good, at all.
Cheers,
--
Pierre
@pierrejoye | http://www.libgd.org
--
PHP Internals - PHP Runtime Development Mailing List
To unsubscribe, visit: http://www.php.net/unsub.php
on fixing things.
This RFC is incomplete and unrealistic, besides not taking into
account other opinions. It should go back to discussions and solve the
obvious issues before even thinking about voting on it.
Cheers,
--
Pierre
@pierrejoye | http://www.libgd.org
--
PHP Internals - PHP Runtime
take them into accounts too) and get
back to code :)
https://wiki.php.net/rfc/php7_57_roadmap
Cheers,
--
Pierre
@pierrejoye | http://www.libgd.org
--
PHP Internals - PHP Runtime Development Mailing List
To unsubscribe, visit: http://www.php.net/unsub.php
to
rollback the fpm changes, release 5.5.20 and 5.6.4 and keep fpm+ipv6
for master?
It could be a solution, while it brings its lot of issues too.
As Remi said, it would be way better if we stop change so many things in
patch releases.
Cheers,
Pierre
Good point. They will remain in the archives part. We kept them after eol
just in case there was a last min critical update (we had one actually :)
I will remove them asap.
On Nov 15, 2014 1:45 PM, Thomas Hruska thru...@cubiclesoft.com wrote:
PHP 5.3 was removed from the website earlier today
Hi,
On Thu, Nov 6, 2014 at 3:20 AM, Florian Margaine flor...@margaine.com wrote:
Thoughts? Am I thinking too much? Is this idea unfeasible? Is it a good
idea?
Have you missed:
https://wiki.php.net/rfc/releaseprocess
?
Cheers,
--
Pierre
@pierrejoye | http://www.libgd.org
--
PHP
On Nov 6, 2014 11:46 AM, Andrea Faulds a...@ajf.me wrote:
On 5 Nov 2014, at 20:34, Ferenc Kovacs tyr...@gmail.com wrote:
Regardless of those, I think it would be worse from the users POV than
our
current policy where we target no BC breaks in minor/micro versions.
The only exception
/reference/annotations.html
That makes a pretty good base spec.
--
Pierre
@pierrejoye | http://www.libgd.org
--
PHP Internals - PHP Runtime Development Mailing List
To unsubscribe, visit: http://www.php.net/unsub.php
On Nov 4, 2014 8:54 PM, Benjamin Eberlei kont...@beberlei.de wrote:
On Tue, Nov 4, 2014 at 11:28 AM, Pierre Joye pierre@gmail.com wrote:
On Tue, Nov 4, 2014 at 4:21 PM, Stas Malyshev smalys...@sugarcrm.com
wrote:
Hi!
As I do consider personal tastes important, there are times where
On Nov 4, 2014 5:28 AM, Stas Malyshev smalys...@gmail.com wrote:
Hi!
PHP doesn’t need more inconsistency, sure, but we must be practical
here. It is bad if PHP and Hack have the same feature with different
syntax, it will cause developer confusion and further segment the
communities.
On Nov 4, 2014 1:24 AM, Jonah H. Harris jonah.har...@gmail.com wrote:
On Mon, Nov 3, 2014 at 9:11 AM, Chris Wright c...@daverandom.com wrote:
There are no current concrete plans and currently nothing being
seriously
discussed (at least, not publicly; I don't know if anyone has anything
in
On Nov 4, 2014 8:50 AM, Levi Morrison le...@php.net wrote:
Whether the annotation is in a comment or not, the idea of changing
behavior at runtime based on the annotation is pretty magical. I
highly discourage using this type of feature whether it's in a comment
or not.
I will certainly
On Oct 31, 2014 11:48 PM, Miloslav Hůla miloslav.h...@gmail.com wrote:
I agree with Levi, that using FQN in annotations works. And I wrote
reasons why it is wrong. Moreover, IDEs works with aliases in annotations
well. The only missing fragment is, that you cannot access aliases
definitions in
: yes we have a PR list. Which did not work as expected. PRs and
discussions in them should not be considered as noises to the internals list
Cheers,
Pierre
big changes as 5.6 is
stable now, huge changes (and not well tested, builds were broken
f.e.) should be done after (public) discussions, if necessary.
Cheers,
--
Pierre
@pierrejoye | http://www.libgd.org
--
PHP Internals - PHP Runtime Development Mailing List
To unsubscribe, visit: http
On Oct 30, 2014 5:59 PM, Bob Weinand bobw...@hotmail.com wrote:
To add for 3.: Issues where with what I really couldn’t think of
(separate build dir on Linux…) or the issues with a JSON dep or Windows
which I couldn’t test.
For this part, I can get you and Joe full msdn subscription if desired.
will allow us to be more consistent and developer
friendly.
--
Pierre
@pierrejoye | http://www.libgd.org
--
PHP Internals - PHP Runtime Development Mailing List
To unsubscribe, visit: http://www.php.net/unsub.php
,
--
Pierre
@pierrejoye | http://www.libgd.org
--
PHP Internals - PHP Runtime Development Mailing List
To unsubscribe, visit: http://www.php.net/unsub.php
could have spoken to me at that
conference in person, or to any of us in IRC, on any day. You chose to
do what pleased you.
We should be allowed to do the same.
Yes and no, as I wrote earlier in this reply.
Thanks for the great work and let try to sort that out :)
Cheers,
Pierre
On Sat, Oct 25, 2014 at 4:39 PM, Joe Watkins pthre...@pthreads.org wrote:
Pierre,
I wasn't involved in the conversations during it's development very
much. You will have to wait for bob or someone from the phpstorm team to
fill in the blanks. Suffice to say that they found a reason
ways bringing even more troubles and inconsistencies.
Cheers,
--
Pierre
@pierrejoye | http://www.libgd.org
--
PHP Internals - PHP Runtime Development Mailing List
To unsubscribe, visit: http://www.php.net/unsub.php
the conversation so we can
hash out
the details, or get on with other things ;)
Cheers
Joe
--
PHP Internals - PHP Runtime Development Mailing List
To unsubscribe, visit: http://www.php.net/unsub.php
--
Pierre
@pierrejoye | http://www.libgd.org
--
PHP Internals - PHP Runtime Development
install`) I don't know how much PHP 4 legacy which required such
tricks is still in there.
We plan to propose to bundle pickle, that should solve the pecl issue.
Pickle relies strictly on 5.4+.
Cheers,
--
Pierre
@pierrejoye | http://www.libgd.org
--
PHP Internals - PHP Runtime Development Mailing
not the way I see cooperation and support for other php.net
developers.
Cheers,
--
Pierre
@pierrejoye | http://www.libgd.org
--
PHP Internals - PHP Runtime Development Mailing List
To unsubscribe, visit: http://www.php.net/unsub.php
that with Andi. A little ping would have been
nice. Anyway, I will remove the 7 section on the other RFC and go for
it, if there are no other issue we cannot solve before voting,
--
Pierre
@pierrejoye | http://www.libgd.org
--
PHP Internals - PHP Runtime Development Mailing List
To unsubscribe, visit
.
Cheers,
--
Pierre
@pierrejoye | http://www.libgd.org
--
PHP Internals - PHP Runtime Development Mailing List
To unsubscribe, visit: http://www.php.net/unsub.php
On Oct 13, 2014 7:10 PM, Jan Ehrhardt php...@ehrhardt.nl wrote:
Dmitry Stogov in php.internals (Mon, 13 Oct 2014 14:29:06 +0400):
Note, that once we move extension outside of main source tree, only
extension maintainers (if any) will support them.
In the ext/mysql case this will be a bit
On Oct 13, 2014 8:08 PM, Jan Ehrhardt php...@ehrhardt.nl wrote:
Pierre Joye in php.internals (Mon, 13 Oct 2014 14:21:24 +0200):
On Oct 13, 2014 7:10 PM, Jan Ehrhardt php...@ehrhardt.nl wrote:
In the ext/mysql case this will be a bit uncomfortable. If you compile
PHP --with-mysql=mysqlnd
On Oct 11, 2014 4:14 PM, Lester Caine les...@lsces.co.uk wrote:
On 11/10/14 01:18, Andrea Faulds wrote:
What you want is 64-bit data handling. This is arbitrary-bit data
handling. It’s not a “wrong approach”.
So BIGINT on 32 bit platforms will be different to BIGINT on 64 bit
On Oct 11, 2014 3:34 AM, Andrea Faulds a...@ajf.me wrote:
I would vote against any such proposal, and I hope others on the list
would join me in doing so.
I fully agree with you here.
is present?
I feel like writing a completely unnecessary keyword each time I write
a new method for a class.
I guess this was a discussion earlier, though I wasn't able to find
anything about it. Would love to hear, what pdt-internals (re-)think about
that topic.
Me and Pierre have
on windows.php.net, or if you're not planning on
retagging we can just sit tight and wait for the official announcement.
yes, pull them off for now. Only to be in sync with the official
releases, thanks!
--
Pierre
@pierrejoye | http://www.libgd.org
--
PHP Internals - PHP Runtime Development Mailing List
trustworthy imho. I don't see a huge downside here.
I wonder if one could replace that release server with a simple vagrant
setup or similar so the RM can actually create release archives on his
own.
Greetings,
Pierre
--
Pierre Schmitz, https://pierre-schmitz.com
--
PHP Internals - PHP Runtime
On Mon, Sep 29, 2014 at 6:35 PM, Pierre Schmitz pie...@archlinux.de wrote:
Am 29.09.2014 17:04, schrieb Johannes Schlüter:
On Mon, 2014-09-29 at 06:35 -0700, Rasmus Lerdorf wrote:
Actually, some php.net machines have been compromised and prevent us
from releasing 5.6.1.
[...]
Q
to
know if it was held back due to last minute bugs.
Greetings,
Pierre
--
Pierre Schmitz, https://pierre-schmitz.com
--
PHP Internals - PHP Runtime Development Mailing List
To unsubscribe, visit: http://www.php.net/unsub.php
to your patch.
Please do not :) Enough mess with RFC changed while being voting on.
Cheers,
--
Pierre
@pierrejoye | http://www.libgd.org
--
PHP Internals - PHP Runtime Development Mailing List
To unsubscribe, visit: http://www.php.net/unsub.php
, but this should mostly
fix it. Of course, gettype() is still going to return “object” not
“resource”, but I suspect people are more likely to use is_resource().
Is it really necessary? I could imagine a transition with 5.7 for
that, similar to gmp.
Cheers,
--
Pierre
@pierrejoye | http
On Sep 23, 2014 8:07 PM, Leigh lei...@gmail.com wrote:
On 23 September 2014 17:36, Park Framework park.framew...@gmail.com
wrote:
If you do not update in PHP 7 serialization method, it will never be
updated, the default serialization in PHP 7 will be slow.
To maintain backward
relying on it to process URI/URL.
Cheers,
--
Pierre
@pierrejoye | http://www.libgd.org
--
PHP Internals - PHP Runtime Development Mailing List
To unsubscribe, visit: http://www.php.net/unsub.php
On Sep 24, 2014 10:19 AM, Michael Wallner m...@php.net wrote:
On 24/09/14 08:30, Stas Malyshev wrote:
Hi!
Well, then let's remove this restriction from resources, too.
Not sure what use would it be for resources - resource IDs are not
controlled by user code and for all intents and
bureaucracy hell.
There is no bureaucracy hell but an end to endless discussions,
pressures, and other nonconstructive behaviors. The recent RFC events
about starting, ending, counting are unlucky but easily fixable.
Cheers,
--
Pierre
@pierrejoye | http://www.libgd.org
--
PHP Internals - PHP
.
if somehost.example.com has the MX, it should return true with
checkdnsrr('somehost.example.com'). If example has the MX set to
somehost.example.com or similar, it should return true as well. Or am
I missing your point?
--
Pierre
@pierrejoye | http://www.libgd.org
--
PHP Internals - PHP Runtime Development
anymore. In short, let trash this horrible idea.
Cheers,
--
Pierre
@pierrejoye | http://www.libgd.org
--
PHP Internals - PHP Runtime Development Mailing List
To unsubscribe, visit: http://www.php.net/unsub.php
:
https://github.com/msgpack/msgpack-php
--
PHP Internals - PHP Runtime Development Mailing List
To unsubscribe, visit: http://www.php.net/unsub.php
--
Pierre
@pierrejoye | http://www.libgd.org
--
PHP Internals - PHP Runtime Development Mailing List
To unsubscribe, visit: http
by default. Similar scenario to putting in Zend OpCache by
default instead of APC.
Pierre, do you see merit on including insert best overall serializer lib
here by default in PHP7 ?
Not really, not because it is not good but because there is always be a
better one. We can't break format in every
On Sep 23, 2014 8:17 PM, Zeev Suraski z...@zend.com wrote:
I'd welcome better suggestions if anybody has any. I think the complete
lack of metrics and exceptionally low barrier to voting is a much bigger
problem.
Please point me at a vote where the author is not part of what you defined
be implemented, as I'm currently undecided. Also please feel free
to point out any areas of improvement for the RFC itself.
I am not sure which problem this RFC tries to solve, do you have any
example showing the issues please?
Cheers,
--
Pierre
@pierrejoye | http://www.libgd.org
--
PHP Internals - PHP
On Mon, Sep 22, 2014 at 9:07 AM, Kris Craig kris.cr...@gmail.com wrote:
On Sep 21, 2014 11:52 PM, Pierre Joye pierre@gmail.com wrote:
Well, for what I can see users already take into account this part of
the issue then:
https://github.com/search?l=phpq=checkdnsrrtype=Codeutf8=%E2%9C%93
On Mon, Sep 22, 2014 at 10:56 AM, Kris Craig kris.cr...@gmail.com wrote:
On Sep 22, 2014 1:09 AM, Pierre Joye pierre@gmail.com wrote:
On Mon, Sep 22, 2014 at 9:07 AM, Kris Craig kris.cr...@gmail.com wrote:
On Sep 21, 2014 11:52 PM, Pierre Joye pierre@gmail.com wrote:
Well
On Mon, Sep 22, 2014 at 11:02 AM, Peter Cowburn petercowb...@gmail.com wrote:
If you say so. Still, the asking of individuals to remove their votes so
that the tally is in you favour is inexcusable.
did I miss something? What is this request to remove votes thing?
--
Pierre
@pierrejoye
to propose a
solution, avoiding this.
--
Pierre
@pierrejoye | http://www.libgd.org
--
PHP Internals - PHP Runtime Development Mailing List
To unsubscribe, visit: http://www.php.net/unsub.php
On Mon, Sep 22, 2014 at 11:56 AM, Kris Craig kris.cr...@gmail.com wrote:
On Sep 22, 2014 2:16 AM, Pierre Joye pierre@gmail.com wrote:
On Mon, Sep 22, 2014 at 10:56 AM, Kris Craig kris.cr...@gmail.com wrote:
On Sep 22, 2014 1:09 AM, Pierre Joye pierre@gmail.com wrote:
On Mon
On Sep 22, 2014 3:31 PM, Derick Rethans der...@php.net wrote:
On Mon, 22 Sep 2014, Michael Wallner wrote:
On 2014-09-22 14:08, Andrea Faulds wrote:
On 22 Sep 2014, at 12:06, Derick Rethans der...@php.net wrote:
I would also like to point out that, just like a 8:8 vote is not a
On Sep 22, 2014 3:29 PM, Derick Rethans der...@php.net wrote:
On Mon, 22 Sep 2014, Andrey Andreev wrote:
On Mon, Sep 22, 2014 at 3:10 PM, Andrea Faulds a...@ajf.me wrote:
On 22 Sep 2014, at 12:32, Derick Rethans der...@php.net wrote:
On Sat, 20 Sep 2014, Andrea Faulds wrote:
/no vote.
Never worked before and it will suddenly work? I am open to know how
one can make it works. Unless you mean to go back to individual
deciding everything for a given area or ext.
Cheers,
--
Pierre
@pierrejoye | http://www.libgd.org
--
PHP Internals - PHP Runtime Development Mailing List
On Sep 22, 2014 8:56 PM, Zeev Suraski z...@zend.com wrote:
Last, the 2nd sub-bullet of the 2nd bullet (regular participant of
internals discussions) is especially problematic - as it basically pulls
the barrier to entry to nothing, and is the opposite of well-defined.
When
we revise the
On Sep 22, 2014 8:56 PM, Zeev Suraski z...@zend.com wrote:
account for people contributing docs and other types of submissions. I'd
also consider adding a requirement for contributing at least X commits
(say
20 or 50) so that someone who did a one-off or two-off patch won't have
the
same
?
Is the actual code used by the parser exposed? If yes it will be
somehow bad as ext maintainers relying on this will need two different
builds. I do not think there are many affected exts out there tho'. If
not, then it is easy :)
--
Pierre
@pierrejoye | http://www.libgd.org
--
PHP Internals
On Sep 22, 2014 10:05 PM, Levi Morrison le...@php.net wrote:
I don't want to say anything else here, as technically this is thread
hijacking (sorry Andrea) but I am very interested in collaborating with
anyone who would like to try to improve the RFC process. Perhaps reply to
me off-list if you
there. There was also
http://www.php-vote.com/browse/latest showing in the top requests.
In any case, this endless discussion leads nowhere and we are not going to
have anything done using such debates and arguing.
Cheers,
--
Pierre
On Sep 23, 2014 1:23 AM, Park Framework park.framew...@gmail.com wrote:
PHP serialization is slowest in PHP Session, clients NoSQL, ...
I would like to have in PHP 7, a new serialization algorithm or custom
handler to serialize.
The latter is already possible and there are many good
On Sep 20, 2014 7:07 PM, Andrea Faulds a...@ajf.me wrote:
On 20 Sep 2014, at 06:06, Pierre Joye pierre@gmail.com wrote:
I am not sure what brings you here but the idea of community votes was
one
of the top thing when we introduced the voting RFC.
I should've made clear I'm
possible ways to block or push
RFCs is getting counter productive and produce a bad experience.
Cheers,
Pierre
On Sep 21, 2014 10:48 AM, Xinchen Hui larue...@php.net wrote:
On Sun, Sep 21, 2014 at 11:33 AM, Pierre Joye pierre@gmail.com
wrote:
Hi,
On Sep 21, 2014 10:08 AM, Xinchen Hui larue...@php.net wrote:
On Sun, Sep 21, 2014 at 11:03 AM, Andrea Faulds a...@ajf.me wrote:
On 21 Sep
.
Cheers,
Pierre
.
Cheers,
Pierre
901 - 1000 of 4120 matches
Mail list logo
