Am 12.09.2013 14:18 schrieb "Johannes Schlüter" :
>
> Hi,
>
> there is some talk about contributing new features and roadmaps for
> PHP. What is missing is talk about maintenance.
>
> PHP is developing really fast, if you consider the distribution we
> reach.
>
> Let's take a look at the last
Am 12.9.2013 um 22:44 schrieb Johannes Schlüter :
> On Wed, 2013-09-11 at 23:21 +0200, Bob Weinand wrote:
>> Hi!
>>
>> I tried to widen the naming possibilities by allowing to use keywords
>> as identifiers (for function names, class names, label (goto)
>> names, ...) where possible. It doesn't br
Am 12.9.2013 um 22:59 schrieb Pierre Joye :
> On Thu, Sep 12, 2013 at 10:55 PM, Nikita Popov wrote:
>> Supporting different sets of keywords in
>> different locations is pretty confusing. Imho we should add this kind of
>> support only in places where a) we can support all keywords and b) it is
>>
On 12/09/2013 22:16, Robert Froslev wrote:
Hello,
Hi.
I have found your website wiki.horde.org when searching the web on the topics
related to my website theme.
I'm sorry, you must be mistaken. The only wiki. here is wiki.php.net.
This is also not the email address for php.net. It is the
On Thu, Sep 12, 2013 at 10:44 PM, Johannes Schlüter
wrote:
> I often stumbled over the annoyance of this limitation and I know many
> users want it, I'm not convinced about adding it, though.
>
> One reason is the "where (easily) possible" part. Right now we have a
> simple rule "keywords can't be
On Thu, Sep 12, 2013 at 10:55 PM, Nikita Popov wrote:
> I tend to agree with Johannes.
I tend to agree too but I never really liked this keywords restriction.
> Supporting different sets of keywords in
> different locations is pretty confusing. Imho we should add this kind of
> support only in
hi Florin,
On Wed, Sep 11, 2013 at 12:44 PM, Florin Patan wrote:
> This morning I read something that's not fun:
> https://twitter.com/ircmaxell/status/376027280562073600
>
> Yet another good contributor leaves this community (not the whole PHP
> community) because of the way things are done her
Hello,
I have found your website wiki.horde.org when searching the web on the topics
related to my website theme.
I must say your site content is very good and I think we would benefit much
from possible partnership - for example link exchange. This would bring more
targeted traffic to our sites
On Wed, 2013-09-11 at 23:21 +0200, Bob Weinand wrote:
> Hi!
>
> I tried to widen the naming possibilities by allowing to use keywords
> as identifiers (for function names, class names, label (goto)
> names, ...) where possible. It doesn't break any BC.
I often stumbled over the annoyance of this
hi Derick,
On Wed, Sep 11, 2013 at 3:19 PM, Derick Rethans wrote:
> On Wed, 11 Sep 2013, Daniel Basten wrote:
>
>> cite: "I hope this is a joke."
>>
>> i guess that is the stuff they where talking about.
>
> Not following etiquette is one of the things that annoys people. And you
> just violated
hi,
On Thu, Sep 12, 2013 at 4:34 PM, Bob Weinand wrote:
> As Benjamin suggested, here the best running times of "time phpunit" in the
> symfony test suite:
>
> With patch:
> real 0m30.885s
> user 0m14.713s
> sys 0m2.123s
>
> Without patch:
> real 0m31.380s
> user 0m14.865s
> sys 0m2.170s
>
> Se
Le 12/09/2013 16:52, Michael Wallner a écrit :
Have you talked to Michael yet and see if he could work on some bugs and/or
feature requests lacking developers?
I'm too much of a donkey to drive PHP alone, but thank you for your
confidence :)
You're welcome ;)
I wasn't thinking of putting y
On 12 September 2013 16:34, Bob Weinand wrote:
> As Benjamin suggested, here the best running times of "time phpunit" in the
> symfony test suite:
>
> With patch:
> real 0m30.885s
> user 0m14.713s
> sys 0m2.123s
>
> Without patch:
> real 0m31.380s
> user 0m14.865s
> sys 0m2.170s
>
> Seems that i
On 12 September 2013 13:43, Pascal Chevrel wrote:
> Le 12/09/2013 04:46, Rasmus Lerdorf a écrit :
>
>> On 09/11/2013 05:34 PM, Florin Patan wrote:
>>>
>>> - lack of a clear roadmap: as I said earlier, can someone really tell
>>> what's in the next two versions of php from now
>>
>>
>> That's never
Am 12.9.2013 um 15:06 schrieb Michael Wallner :
> On 12 September 2013 14:56, Bob Weinand wrote:
>> A little benchmark here: https://gist.github.com/bwoebi/6536824
>>
>> Here I picked always the best from 10 times running.
>>
>> With patch:
>> root# ./sapi/cli/php microbench.php
>> Took for 1000
Bob,
you should maybe run the testsuite for example of symfony2, it has 11k
tests and runs not too long. This should be a good benchmark. Phpunit
reports the execution times.
greetings
Benjamin
On Thu, Sep 12, 2013 at 3:06 PM, Michael Wallner wrote:
> On 12 September 2013 14:56, Bob Weinand
On 12 September 2013 14:56, Bob Weinand wrote:
> A little benchmark here: https://gist.github.com/bwoebi/6536824
>
> Here I picked always the best from 10 times running.
>
> With patch:
> root# ./sapi/cli/php microbench.php
> Took for 1 iterations: 8.6687519550323 seconds
>
> Without patch:
>
On Sun, Sep 8, 2013 at 1:26 AM, Gustavo Lopes wrote:
> On 06-09-2013 23:54, Nikita Popov wrote:
>
>> On Fri, Sep 6, 2013 at 11:23 PM, Gustavo Lopes > >wrote:
>>
>>>
>>> I think the correct course of action is just to drop support for extra
>>> named arguments. Just add an extra array argument to t
Am 12.9.2013 um 09:10 schrieb Michael Wallner :
> On 11 September 2013 23:21, Bob Weinand wrote:
>> Hi!
>>
>> I tried to widen the naming possibilities by allowing to use keywords as
>> identifiers (for function names, class names, label (goto) names, ...) where
>> possible. It doesn't break
Hi,
there is some talk about contributing new features and roadmaps for
PHP. What is missing is talk about maintenance.
PHP is developing really fast, if you consider the distribution we
reach.
Let's take a look at the last few years and the amount of language
changes. PHP 5.2 was releases
Florin Patan wrote:
That said, maybe after 5.6 release it would be a good time to have a
meeting and talk about future PHP versions and how we get there? I can
suggest Berlin as a place to do it, there's plenty of activity here,
lots of startups using PHP and a pretty nice city.
You see that I
Le 12/09/2013 04:46, Rasmus Lerdorf a écrit :
On 09/11/2013 05:34 PM, Florin Patan wrote:
- lack of a clear roadmap: as I said earlier, can someone really tell
what's in the next two versions of php from now
That's never going to happen. We don't have paid developers that we can
assign tasks t
On Thu, Sep 12, 2013 at 11:02 AM, Lester Caine wrote:
> Rasmus Lerdorf wrote:
>>
>> That's never going to happen. We don't have paid developers that we can
>> assign tasks to. We have volunteers who work on things they need or find
>> fun to work on. We can't possibly provide a solid road map two
On Thu, Sep 12, 2013 at 4:46 AM, Rasmus Lerdorf wrote:
> On 09/11/2013 05:34 PM, Florin Patan wrote:
>> - lack of a clear roadmap: as I said earlier, can someone really tell
>> what's in the next two versions of php from now
>
> That's never going to happen. We don't have paid developers that we c
Why not both?
The list should and will remain, but I see no issue in using the same
inbox to start/reply-to a thread; it's been done, it can be done!
And I don't think it's just about keeping people who like one or the
other more, but rather allowing a quick read over the conversation in
a threaded
Rasmus Lerdorf wrote:
That's never going to happen. We don't have paid developers that we can
assign tasks to. We have volunteers who work on things they need or find
fun to work on. We can't possibly provide a solid road map two (I assume
you mean major) versions out.
The conflict here is the
Authorities don't run away.
On Thu, Sep 12, 2013 at 3:25 AM, Pascal Chevrel wrote:
> e 12/09/2013 07:40, Daniel Brown a écrit :
>
> On Thu, Sep 12, 2013 at 12:10 AM, Seva Lapsha
>> wrote:
>>
>>> PHP is a collective mind. Any dictatorship would mean a degradation for
>>> it.
>>> If you don't li
Le 12/09/2013 07:40, Daniel Brown a écrit :
On Thu, Sep 12, 2013 at 12:10 AM, Seva Lapsha wrote:
PHP is a collective mind. Any dictatorship would mean a degradation for it.
If you don't like how it's managed, there is an easy path:
1. Earn authority.
2. Propose a change.
3. Implement it.
4. Ma
On 09/12/2013 06:43 AM, Philip Sturgeon wrote:
> As for the comments about the FIG made by others, I agree with Larry
> in that we're doing a pretty good job at trying to build on the
> example set forward by internals. Self moderation and workflow are two
> important factors to the group, and I d
e 12/09/2013 07:40, Daniel Brown a écrit :
On Thu, Sep 12, 2013 at 12:10 AM, Seva Lapsha wrote:
PHP is a collective mind. Any dictatorship would mean a degradation for it.
If you don't like how it's managed, there is an easy path:
1. Earn authority.
2. Propose a change.
3. Implement it.
4. Mai
On 11 September 2013 23:21, Bob Weinand wrote:
> Hi!
>
> I tried to widen the naming possibilities by allowing to use keywords as
> identifiers (for function names, class names, label (goto) names, ...) where
> possible. It doesn't break any BC.
>
> Furthermore when BC needs to be broken in futu
Bob Weinand wrote:
> I tried to widen the naming possibilities by allowing to use keywords as
> identifiers (for function names, class names, label (goto) names, ...) where
> possible. It doesn't break any BC.
Is the token still T_LIST/T_DEFAULT given that example above, or would
those be T_STRI
Hey Bob,
I like it very much, i flew over the patch to see what would be possible,
and that includes many of the points that annoy me most of the time :-)
greetings
Benjamin
On Wed, Sep 11, 2013 at 11:21 PM, Bob Weinand wrote:
> Hi!
>
> I tried to widen the naming possibilities by allowing to
33 matches
Mail list logo
