On 05/10/2016 03:48 PM, Benjamin Eberlei wrote:
On Tue, May 10, 2016 at 8:29 PM, Dmitry Stogov wrote:
Hi internals,
I've started voting on "PHP Attributes" RFC.
https://wiki.php.net/rfc/attributes
In my opinion, "PHP Attributes" might be a smart tool for PHP extension,
but it's not going
On 05/12/2016 08:27 PM, guilhermebla...@gmail.com wrote:
Hi internals,
PHP 7 leverages a lot the performance internally and many PHP applications
in the wild. Much of these improvement came by experimentation through
PHPNG and the usage of efficient data structures internally. This idea of
perfo
On 05/14/2016 07:42 PM, François Laupretre wrote:
Le 13/05/2016 à 20:16, Sara Golemon a écrit :
for a potential solution to such a long-time issue as argument ordering
sadness, IMHO, it's worth the pain. I am currently doing it and I'll
send
you the list when it is ready.
Awesome. Even if n
On Sun, May 15, 2016 at 11:20 AM, Nikita Nefedov wrote:
> why would you need to support a $this->fieldName case though?
>
Because to not support it would be to deliberately design in a new
flavor of inconsistency into the language. $obj->memb is a property
access in PHP. Making it suddenly mean "
Hi internals,
The RFC
https://wiki.php.net/rfc/forbid_dynamic_scope_introspection
is now in voting. The vote closes on 2016-05-24 with a required majority of
2/3.
Nikita
> On 15 May 2016, at 20:29, Dan Ackroyd wrote:
>
> Hello,
>
> I've opened the voting for the Closure from callable RFC -
> https://wiki.php.net/rfc/closurefromcallable
>
> Just to note, some people I've spoken to have expressed a desire to
> have a more powerful syntax where 'bare' function na
Hello,
I've opened the voting for the Closure from callable RFC -
https://wiki.php.net/rfc/closurefromcallable
Just to note, some people I've spoken to have expressed a desire to
have a more powerful syntax where 'bare' function names are used,
like:
callable(someFunctionName)
callable($this->me
2016-05-15 16:21 GMT+02:00 Rasmus Schultz :
> > As a downside, you can't implement it in a normal class anymore and just
> use
> > an instance of that class.
>
> I see that as a plus, because, as a you said:
>
> > That's why you call it with the method name of the interface
>
> Your logic is circu
> As a downside, you can't implement it in a normal class anymore and just use
> an instance of that class.
I see that as a plus, because, as a you said:
> That's why you call it with the method name of the interface
Your logic is circular - you also said:
> As a downside, you can't implement i
2016-05-15 12:05 GMT+02:00 Rasmus Schultz :
> I know you're already voting on this, but I'd like to throw in a
> couple of late comments.
>
> My main problem with this RFC is the use of the interface keyword for
> something that almost by definition is not an interface.
>
> An interface is a set o
I know you're already voting on this, but I'd like to throw in a
couple of late comments.
My main problem with this RFC is the use of the interface keyword for
something that almost by definition is not an interface.
An interface is a set of methods, but an anonymous function is just
one function
Morning internals,
Functional interfaces has been moved to voting stage, please
participate.
http://wiki.php.net/rfc/functional-interfaces#vote
Cheers
Joe
12 matches
Mail list logo
