Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:54380
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Received-SPF: pass (pb1.pair.com: domain gmail.com designates 209.85.216.177 as permitted sender)
MIME-Version: 1.0
In-Reply-To: <CAFt2z-kRdCrD3EDqWLdQKVcyfRRZTZvtMc9Z+etDSw+2tcaATQ@mail.gmail.com>
References: <CAMyk_AZQ8cJ+iVZ=9x76kYCi4n5_FYyAg9JQQnL_BJhBUX6cCg@mail.gmail.com>
	<4E3A48F2.4000503@lerdorf.com>
	<CAMyk_AYxuK=o1s-HD7MGjV8u8KLksxgUfrvsx0qZdTO1MEuqJw@mail.gmail.com>
	<4E3A8014.1030503@rotorised.com>
	<1312457975.1541.7.camel@guybrush>
	<CAMyk_AZ+Ym2V+JZxGV3Fxv1sNhqGpk4KXtJBDga1BuXdjA0vmg@mail.gmail.com>
	<4E3A9549.6010803@daylessday.org>
	<CAGU04mJGQQQPn5EzTzjSQuXeHEzS57_Af6EM9yLw5eH7uiCW5g@mail.gmail.com>
	<alpine.DEB.2.02.1108041403190.5758@whisky>
	<4E3A9AA9.4010802@daylessday.org>
	<CAMWw8k_9VVD9BNLbKr_VXUTdDyTe-i2RSQeUkG=-vWWHfYWjcw@mail.gmail.com>
	<CAFt2z-kRdCrD3EDqWLdQKVcyfRRZTZvtMc9Z+etDSw+2tcaATQ@mail.gmail.com>
Date: Thu, 4 Aug 2011 20:04:54 +0100
Message-ID: <CAKxcST-ob6+o3_q3mzzrcp3Jnkb8WpAxq05x+3z=9QX8HWNQmg@mail.gmail.com>
To: dukeofgaming <dukeofgaming@gmail.com>
Cc: Gwynne Raskind <gwynne@darkrainfall.org>, Antony Dovgal <tony@daylessday.org>, 
	internals@lists.php.net
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable
Subject: Re: [PHP-DEV] An implementation of a short syntax for closures
From: dragoonis@gmail.com (Paul Dragoonis)

On Thu, Aug 4, 2011 at 7:54 PM, dukeofgaming <dukeofgaming@gmail.com> wrote=
:
> On Thu, Aug 4, 2011 at 1:47 PM, Gwynne Raskind <gwynne@darkrainfall.org>w=
rote:
>
>> On Thu, Aug 4, 2011 at 09:12, Antony Dovgal <tony@daylessday.org> wrote:
>> >>> =A0Btw, am I the only one to whom the proposed syntax seems kinda
>> >>> hieroglyphic?
>> >> No. I don't see at all why we need this, just like I don't see why we
>> >> needed an alternative (short) syntax for arrays. This kind of syntax
>> >> additions that add *no* functionality, should not be in PHP.
>> > Yes, I believe we should stop this stream of alternative syntax propos=
als
>> > and concentrate on fixing existing functionality instead of adding les=
s
>> readable ways to do
>> > the same thing. I would really like to keep PHP code easily readable, =
not
>> to turn it into
>> > perl-ish write-only gibberish.
>>
>> 100% agreed, both about the cryptic nature of the proposed syntax and
>> the need to focus on fixing existing issues. Strong -1 on a new
>> syntax.

>
>
> Aye, just realized watching the |=3D> reminded me of perl... say, I think=
 that
> is what an aneurysm feels like.
>

One of the downsides to a language like perl was its Readability,
fancy magic symbols and lack of readability in its source code. PHP
has the opposite, very clear and readable C-like code. If PHP moves
towards a more magic syntax language then it would be
counter-productive.

Closures are quirky enough to wrap your eyes/mind around. Making these
more cryptic is very counter-productive.

Like mentioned, the amount of typing is not a problem, its more so
waiting on things to transfer, commit..etc

Very big -1 for me on this one. Please don't let a plethora of PHP
devs release code with this syntax.

Regards,
Paul Dragoonis.