Ho
2008/11/21 Kenan R Sulayman <[EMAIL PROTECTED]>:
> Well, then excuse moi!
> I did not realize the power of php 5.3, yet.
Its still not documented yet, but if you wanna read more about
Closoures in PHP then its RFC might be worth reading:
http://wiki.php.net/rfc/closures
>
> Thanks,
> --
> (c)
Hi!
. end
. prev
. next
. reset
. current
. key
. array_key_exists
. array_unique
. array_flip
. array_walk_recursive
. array_walk
. uksort
. uasort
. usort
. natcasesort
. natsort
Attached is the patch that should restore BC for all those functions
except sorts and array_unique/array_flip (t
Well, then excuse moi!
I did not realize the power of php 5.3, yet.
Thanks,
--
(c) Kenan Sulayman
Freelance Designer and Programmer
Life's Live Poetry
PHP 5.3 has anonymous functions.
James Logsdon
On Fri, Nov 21, 2008 at 2:27 PM, Kenan R Sulayman <[EMAIL PROTECTED]>wrote:
> Hey out there!
> I've got a maybe simple question:
> Where the point of not implementing anonymous functions in php alike
> javascript?
>
> Par example:
> As normally use
Hey out there!
I've got a maybe simple question:
Where the point of not implementing anonymous functions in php alike
javascript?
Par example:
As normally used:
Suggestion:
> More Simple, have a better point of view and a bit easier. <
Your,
--
(c) Kenan Sulayman
Freelance Designer and Program
Hi!
As a PHP user who'd want to migrate to 5.3 sooner than later, and uses
those heavily, I'd rather not see BC breaks in a point release, even
though just like you I see some WTF-s in the old behaviour.
You heavily use natsort on objects? What for?
If natsort covered the entirety of this B
Hi!
As a PHP user who'd want to migrate to 5.3 sooner than later, and uses
those heavily, I'd rather not see BC breaks in a point release, even
though just like you I see some WTF-s in the old behaviour.
You heavily use natsort on objects? What for?
--
Stanislav Malyshev, Zend Software Archit
Hi,
Earlier I proposed this construct which fell on deaf ears, maybe since it means
a new keyword "nameof":
namespace Foo\Bar;
class Baz {}
$name = nameof Baz; // 'Foo\Bar\Baz'
The same expansion to FQN happens for imports/aliases with "use XXX".
I want to suggest an alternative approach whic
Hi!
Hmm, I really think we should simply maintain BC 100% but using the new
BC 100% makes little sense - why usort can accept object but sort can't?
And functions like next/prev are useless with many types of objects.
Especialy think this through for the next
bigger release (presumably PHP
Hmm, I really think we should simply maintain BC 100% but using the
new parameter parsing API and then really think this through for the
next bigger release (presumably PHP 6.0) and come up with a set of
interfaces for objects that allow them to more sensibly work with
functions.
FWIW, I
Hi!
I am just worried that we do not have enough time to really think this
through all the way. So in the end we might end up having to break BC
once more in PHP 6.0. Also its not like we are fixing these bugs because
users were submitting bug tickets about this (or have they?).
Well, some o
On 21.11.2008, at 09:54, Stanislav Malyshev wrote:
bigger release (presumably PHP 6.0) and come up with a set of
interfaces for objects that allow them to more sensibly work with
functions.
We already have set of interfaces. They aren't just used
consistently. And that's a bug. We should
Hi!
Hmm, I really think we should simply maintain BC 100% but using the new
BC 100% makes little sense - why usort can accept object but sort can't?
And functions like next/prev are useless with many types of objects.
Especialy think this through for the next
bigger release (presumably PHP
Hi,
Hmm, I really think we should simply maintain BC 100% but using the
new parameter parsing API and then really think this through for the
next bigger release (presumably PHP 6.0) and come up with a set of
interfaces for objects that allow them to more sensibly work with
functions.
re
14 matches
Mail list logo
