-Original Message-
From: Stanislav Malyshev [mailto:[EMAIL PROTECTED]
Sent: Friday, February 22, 2008 9:21 AM
To: Lukas Kahwe Smith
Cc: Gregory Beaver; Marcus Boerger; [EMAIL PROTECTED]; Evert|Rooftop;
internals@lists.php.net
Subject: Re: [PHP-DEV] RFC: Traits for PHP
Hi!
A
Yes, let's re-open, I'd like to get a closure on that issue (pun
intended).
-Andrei
On Feb 18, 2008, at 8:26 AM, Matvey Arye wrote:
Hi All,
I second this. Can we please re-open the discussion on anonymous
functions as well as closures. That would be an awesome feature.
create_function
Hello Pierre,
Friday, February 22, 2008, 5:14:34 PM, you wrote:
Hi Lukas!
On Fri, Feb 22, 2008 at 4:41 PM, Lukas Kahwe Smith [EMAIL PROTECTED] wrote:
Hello all,
Let me briefly pick on poor David's (unfortunately I could have picked
any number of posts on any given day just as well)
On Fri, 22 Feb 2008, Olivier Hill wrote:
On Fri, Feb 22, 2008 at 11:21 AM, David Coallier [EMAIL PROTECTED] wrote:
Well well well, sorry everyone. I'm just too cool to follow the rules
:) Just kidding, I guess I will change email client and apply my
signature to myself as well :)
On Sat, Feb 23, 2008 at 12:34 PM, Derick Rethans [EMAIL PROTECTED] wrote:
On Fri, 22 Feb 2008, Olivier Hill wrote:
On Fri, Feb 22, 2008 at 11:21 AM, David Coallier [EMAIL PROTECTED] wrote:
Well well well, sorry everyone. I'm just too cool to follow the rules
:) Just kidding, I
Hello Andrei,
+1
Friday, February 22, 2008, 7:00:11 PM, you wrote:
Yes, let's re-open, I'd like to get a closure on that issue (pun
intended).
-Andrei
On Feb 18, 2008, at 8:26 AM, Matvey Arye wrote:
Hi All,
I second this. Can we please re-open the discussion on anonymous
And +1 from me :)
David
Am 23.02.2008 um 12:43 schrieb Marcus Boerger:
Hello Andrei,
+1
Friday, February 22, 2008, 7:00:11 PM, you wrote:
Yes, let's re-open, I'd like to get a closure on that issue (pun
intended).
-Andrei
On Feb 18, 2008, at 8:26 AM, Matvey Arye wrote:
Hi
Hi Andrei,
Am Freitag, den 22.02.2008, 10:00 -0800 schrieb Andrei Zmievski:
Yes, let's re-open, I'd like to get a closure on that issue (pun
intended).
+1. I would love it.
cu, Lars
--
Lars Strojny
Senior Software Developer Media Ventures GmbH (http://mediaventures.de)
signature.asc
Hi,
Ok, since there seems to be controversy about how to best collaborate
on documents like TODO lists, RFC's, README's etc. and I do not want
to piss people of by making final decisions on this in a closed
circle. Here it goes. Honestly I do not think its a big issue either
way as long
Do we have a working patch somewhere then?
-Andrei
On Feb 23, 2008, at 12:43 PM, Marcus Boerger wrote:
Hello Andrei,
+1
Friday, February 22, 2008, 7:00:11 PM, you wrote:
Yes, let's re-open, I'd like to get a closure on that issue (pun
intended).
-Andrei
--
PHP Internals - PHP
On Sat, Feb 23, 2008 at 5:09 PM, Andrei Zmievski [EMAIL PROTECTED] wrote:
Do we have a working patch somewhere then?
Did we not get one from Wez? and an alternative from I don't remember :)
--
Pierre
http://blog.thepimp.net | http://www.libgd.org
--
PHP Internals - PHP Runtime Development
Am 23.02.2008 um 17:13 schrieb Pierre Joye:
On Sat, Feb 23, 2008 at 5:09 PM, Andrei Zmievski [EMAIL PROTECTED]
wrote:
Do we have a working patch somewhere then?
Did we not get one from Wez? and an alternative from I don't
remember :)
http://news.php.net/php.internals/34216
I think the
Hi,
I came across one piece of information on aliasing that may not be
obvious at first and therefore should probably be explicitly stated in
the RFC and in the manual when this makes it into the core.
Quoting http://www.iam.unibe.ch/~scg/Archive/Papers/Scha03aTraits.pdf:
Note that because
Gregory Beaver wrote:
So, as you can see, all of the trait methods are available as regular
methods except for A::a which is overridden by B::a. If the order were
reversed, i.e. traits B, A then $a-a() would instead call A::a.
I could see this becoming a problem when it plays along with
2008/2/24, Andrei Zmievski [EMAIL PROTECTED]:
Do we have a working patch somewhere then?
Hi, I have added support for closures to my patches.
http://www.opendogs.org/pub/php-5.3-080223-anon.patch
http://www.opendogs.org/pub/php-6.0-080223-anon.patch
Hi,
Andi Gutmans schrieb:
I don't think so. I think the value here is not copypaste but to be
able to encapsulate some functionality which a class can be
decorated with. Giving a basic storage mechanism to that would be
very beneficial in a large amount of uses. Again, I am proposing
private
Hi,
The above presents a problem if trait2 contains conflicting method
names, but a simple way to solve it would be to automatically alias
methods by prepending traitname::
?php
trait trait1 { function a(){}}
trait trait2 { function a(){}}
class Blah extends ... implements ... traits trait1,
I think we have to be very clear whether we are going to provide just a
sexier notation for anonymous functions or closures (and if the latter
what the semantics are).
Just doing one and not figuring out the long term piece doesn't make
sense because we may end up having two completely distinct
Hi,
Steph Fox schrieb:
All I'm seeing here is people with CS degrees saying trait would be
cool. What about us peasants? Or am I the last living peasant? :\
That's possible, I suppose.
Sell it to me?
A very cool thing of traits is the flattening property ensuring that
there is no
Hi,
Christian Schneider schrieb:
I can see two
use cases for aliasing:
1) An interface uses a different name than the
trait implements. Not sure that's a software design problem trait should
try to solve.
Well, no, aliasing shouldn't be used to achieve this, think it would be
better to add
Hi,
Markus Fischer schrieb:
Hi,
generally asking, how would Reflection act on traits? Can this be
detected or will the information be lost after a class has been
assembled? E.g. detect if a certain method comes from a trait and which
one?
think will work on the reflection part when details
Another detail: The implementation of the parser changes should still
allow a class or function called trait, i.e. trait should only be a
keyword at specific positions in the source to avoid unneccesary BC
breaks. The current patch has this BC problem.
This is not possible to implement, having
Hi!
In my opinion, traits is a thing developers has only to be aware of if
they really did like to use them. (iff proper tool support is available.
Guess it wouldn't be that way for VIM users, for example)
I have little experience about how Smalltalk users look on other's code.
I know,
23 matches
Mail list logo
