Am 06.08.2014 um 06:38 schrieb Sara Golemon:
> https://wiki.php.net/rfc/switch.default.multiple
Makes sense to me; +1.
--
PHP Internals - PHP Runtime Development Mailing List
To unsubscribe, visit: http://www.php.net/unsub.php
https://wiki.php.net/rfc/switch.default.multiple
'Cause this code is silly (even if it had case blocks), but we allow it:
switch ($expr) {
default:
notExecuted();
break;
default:
executed();
}
--
PHP Internals - PHP Runtime Development Mailing List
To unsubscribe, visit: http://
On 30/07/2014 04:31, Andrea Faulds wrote:
Good evening,
The intdiv RFC is put to the vote, with separate votes for the integer division
operator (%%) and intdiv function, the latter as a fallback. I would highly
encourage you to read the discussion in the “[RFC] intdiv()” thread and the
whole
Closure apply
On Aug 5, 2014 8:13 PM, "Andrea Faulds" wrote:
>
> On 5 Aug 2014, at 18:51, Pierre Joye wrote:
>
> > For your RFC, given other solutions, i fail to find one
>
> To which RFC do you refer?
>
> --
> Andrea Faulds
> http://ajf.me/
>
>
>
>
>
On 5 Aug 2014, at 18:51, Pierre Joye wrote:
> For your RFC, given other solutions, i fail to find one
To which RFC do you refer?
--
Andrea Faulds
http://ajf.me/
--
PHP Internals - PHP Runtime Development Mailing List
To unsubscribe, visit: http://www.php.net/unsub.php
On Aug 5, 2014 7:41 PM, "Andrea Faulds" wrote:
>
>
> On 5 Aug 2014, at 18:40, Pierre Joye wrote:
>
> > On Aug 5, 2014 6:40 PM, "Andrea Faulds" wrote:
> > > Side note, but that’s because __invoke on Closure doesn’t actually
exist. It’s a method that is created by trying to access it and ceases to
On 5 Aug 2014, at 18:40, Pierre Joye wrote:
> On Aug 5, 2014 6:40 PM, "Andrea Faulds" wrote:
> > Side note, but that’s because __invoke on Closure doesn’t actually exist.
> > It’s a method that is created by trying to access it and ceases to exist
> > once called. Freaky, right?
>
> Do you h
Hi Andrea,
On Aug 5, 2014 6:40 PM, "Andrea Faulds" wrote:
>
>
> On 5 Aug 2014, at 17:08, Marco Pivetta wrote:
>
> >
> > On 5 August 2014 18:01, Ralph Schindler
wrote:
> > At the risk of stating the obvious, can’t you just use
$f->bar->__invoke()?
> >
> > >Actually, it was not immediately obviou
On 5 Aug 2014, at 17:08, Marco Pivetta wrote:
>
> On 5 August 2014 18:01, Ralph Schindler wrote:
> At the risk of stating the obvious, can’t you just use $f->bar->__invoke()?
>
> >Actually, it was not immediately obvious that __invoke() was a method from
> >the docs as it is a side-note and
On 5 August 2014 18:01, Ralph Schindler wrote:
> At the risk of stating the obvious, can’t you just use $f->bar->__invoke()?
>>
>
> Actually, it was not immediately obvious that __invoke() was a method from
> the docs as it is a side-note and not in the class signature breakout.
> Oops! ;)
>
> ht
At the risk of stating the obvious, can’t you just use $f->bar->__invoke()?
Actually, it was not immediately obvious that __invoke() was a method
from the docs as it is a side-note and not in the class signature
breakout. Oops! ;)
http://php.net/manual/en/class.closure.php
That said, call()
On 5 August 2014 17:50, Andrea Faulds wrote:
>
> On 5 Aug 2014, at 16:20, Ralph Schindler wrote:
>
> > "->call()" would facilitate the following syntax, which I'd argue has
> greater semantic meaning than the call_user_func() variant:
> >
> > $f->bar->call()->call();
>
> At the risk of stating
On 5 Aug 2014, at 16:20, Ralph Schindler wrote:
> "->call()" would facilitate the following syntax, which I'd argue has greater
> semantic meaning than the call_user_func() variant:
>
> $f->bar->call()->call();
At the risk of stating the obvious, can’t you just use $f->bar->__invoke()?
--
An
Andrea + Marco
Is the advantage of `Closure#call()` only performance? Because I don't see
other advantages otherwise, and I don't think the performance impact is
relevant.
I like the proposal, but with some modifications. I am unsure if there
is another RFC out there on function de-referenci
Hi internals,
I have opened a PR in april but since that there is no process on it.
Please tell me if there are open questions / todos.
https://github.com/php/php-src/pull/659
Marc
--
PHP Internals - PHP Runtime Development Mailing List
To unsubscribe, visit: http://www.php.net/unsub.php
On Tue, Aug 5, 2014 at 2:14 PM, Pascal Chevrel
wrote:
> Le 05/08/2014 14:01, Pascal Chevrel a écrit :
>
> Le 05/08/2014 13:41, Dmitry Stogov a écrit :
>>
>>> Now it must be completely fixed in git.
>>>
>>> Thanks. Dmitry.
>>>
>>>
>> Thanks Dmitry, will the .deb package be soon updated so as that
Le 05/08/2014 14:01, Pascal Chevrel a écrit :
Le 05/08/2014 13:41, Dmitry Stogov a écrit :
Now it must be completely fixed in git.
Thanks. Dmitry.
Thanks Dmitry, will the .deb package be soon updated so as that I can
test that the issue is resolved on my side?
Actually, shouldn't 'php -i'
Le 05/08/2014 13:41, Dmitry Stogov a écrit :
Now it must be completely fixed in git.
Thanks. Dmitry.
Thanks Dmitry, will the .deb package be soon updated so as that I can
test that the issue is resolved on my side?
Regards
Pascal
--
PHP Internals - PHP Runtime Development Mailing List
To
Now it must be completely fixed in git.
Thanks. Dmitry.
On Mon, Aug 4, 2014 at 9:44 PM, Dmitry Stogov wrote:
> We can disable immutable arrays when opcache not loaded or disabled.
> But it's going to be difficult to disable them when script can't fit into
> SHM, because at the moment of compil
I am a Chinese, although my English is not very good, use the translation tools
only, but that doesn\'t stop me from loving PHP, PHP is a powerful
language, I hope what I can do for him, even if he paid much effort, I also not
to hesitate to
--
PHP Internals - PHP Runtime Development Mailing
20 matches
Mail list logo
