I'm growing to like the idea myself. It may create new opportunities for
bad practices, but I don't think it's the concern of internals to police
how people may or may not use a feature. There are also I think a few
things that would need to be addressed before this would be ready for the
real
On 09/25/2013 09:59 AM, Terence Copestake wrote:
I'm growing to like the idea myself. It may create new opportunities for
bad practices, but I don't think it's the concern of internals to police
how people may or may not use a feature. There are also I think a few
things that would need to be
1) Anonymous classes in PHP would support a constructor, so I don't see
the need for use to be utilized here, it would just clutter declarations
and the patch.
This works, but it's more effort for the programmer and arguably just
moving the clutter from the declaration to the constructor.
On 09/25/2013 02:02 PM, Terence Copestake wrote:
1) Anonymous classes in PHP would support a constructor, so I don't see
the need for use to be utilized here, it would just clutter declarations
and the patch.
This works, but it's more effort for the programmer and arguably just
moving the
Why couldn't this be implemented on userland again? I don't feel this
is a language level issue.
On Wed, Sep 25, 2013 at 8:55 AM, Yasuo Ohgaki yohg...@ohgaki.net wrote:
Hi Mike,
On Wed, Sep 25, 2013 at 2:16 PM, Mike Willbanks pen...@gmail.com wrote:
Each and every type of prevention measure
hi!
On Sun, Sep 22, 2013 at 11:39 PM, Joe Watkins krak...@php.net wrote:
Morning All,
https://wiki.php.net/rfc/anonymous_classes
I'd like to hear thoughts regarding the addition of anonymous classes,
patch included.
Thanks for your proposal and work.
If you did not yet update your RFC I
Hi Madara,
On Thu, Sep 26, 2013 at 7:49 AM, Madara Uchiha mad...@tchizik.com wrote:
Why couldn't this be implemented on userland again? I don't feel this
is a language level issue.
PHP is not only language, but also meta framework.
It is better to think as how framework support session.
Hi,
I've updated my patch to allow a range of values to be passed as the third
argument: pass key, pass value or pass both.
Instead of using OR-able constants, I went with an enumeration type because
there are only going to be three options; it just felt wrong to have
`ARRAY_FILTER_USE_KEY |
