Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:63127
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Received-SPF: pass (pb1.pair.com: domain gmail.com designates 209.85.215.170 as permitted sender)
MIME-Version: 1.0
Sender: sebastian.krebs.berlin@gmail.com
In-Reply-To: <50593266.5010802@mrclay.org>
References: <50593266.5010802@mrclay.org>
Date: Wed, 19 Sep 2012 08:37:43 +0200
Message-ID: <CALtuQzCBvG7WDrDnBfCzMMdyuuLQYCstQvnMnCCn9vj3xqaMJA@mail.gmail.com>
To: Steve Clay <steve@mrclay.org>
Cc: PHP Internals <internals@lists.php.net>
Content-Type: multipart/alternative; boundary=047d7b343b207b1cc604ca083ebd
Subject: Re: [PHP-DEV] RFC: alternative callback syntax
From: krebs.seb@gmail.com (Sebastian Krebs)

--047d7b343b207b1cc604ca083ebd
Content-Type: text/plain; charset=ISO-8859-1

2012/9/19 Steve Clay <steve@mrclay.org>

> Hello,
>
> https://wiki.php.net/rfc/**alternative_callback_syntax<https://wiki.php.net/rfc/alternative_callback_syntax>is a proposal for a simple alternative syntax for creating function
> callbacks.
>
> The basics: Given a function/method call, replace the argument list with
> "::function". PHP would evaluate this as a callback for the
> function/method, fully resolving any class/function names according to the
> current namespace and any use statements.
>
> In my opinion this syntax would aid readability and benefit users via
> fewer typos and namespace errors, and via (hopefully) better IDE support.
>
>
> I welcome any feedback. I don't have adequate C skills to offer a patch at
> the moment, but I generally read everything I can get my hands on about how
> PHP features are implemented and am not afraid to jump in.
>
> Thanks for your time.
>
> P.S. I've kicked around this idea around for awhile, but Ralph Schindler's
> idea for using ::keyword provided a better path to BC, and more
> attractive/meaningful syntax.
>
> P.P.S. I'm unaware if it's customary to throttle the release of RFCs, so I
> apologize for hogging any attention away from those under discussion.
>
> Steve Clay


Hi,

Beside that I like the idea to get rid of defining callbacks as string (for
the same reason I like 'Classname::class' for classes) I don't like, that
functions will look like classes with a static property "function" then ...

Regards,
Sebastian


>
> --
> http://www.mrclay.org/
>
> --
> PHP Internals - PHP Runtime Development Mailing List
> To unsubscribe, visit: http://www.php.net/unsub.php
>
>


-- 
github.com/KingCrunch

--047d7b343b207b1cc604ca083ebd--