Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:61716
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Received-SPF: pass (pb1.pair.com: domain gmail.com designates 209.85.160.42 as permitted sender)
MIME-Version: 1.0
In-Reply-To: <64388090-395E-4A37-B6C7-4ABE628D0AD7@gmail.com>
References: <CAOhuFvYD8FQw=xbK3hFqi4GYkOvCNzWjuhk2fqwBjKG9n2kuuQ@mail.gmail.com>
	<CAKZjf5T517=_fmrTRo78y4G8cM8-E1jbXfLcN3Z8H44mBjg9rQ@mail.gmail.com>
	<CA+Ky_uMv7HN44oXK29XtQNQLyFSn_rPb5jOrDyJrXFau30=LWw@mail.gmail.com>
	<CAKZjf5T8o-TBcur=+wQH7d_HfRDVJHuvn4oCFHo4xv0cGXU5Gg@mail.gmail.com>
	<4024424F-2D65-41EA-8E18-B2B8FCE94754@gmail.com>
	<CAKZjf5Tgij9PraeJ_W7qNwEbGtxcdONRDG48-w8e7EyGCZ4VYA@mail.gmail.com>
	<64388090-395E-4A37-B6C7-4ABE628D0AD7@gmail.com>
Date: Tue, 24 Jul 2012 20:09:13 +0200
Message-ID: <CAKZjf5T6Eutx47Gg8=JBBEUqi3ghYqd-UoqY78EFb4K-SwATgg@mail.gmail.com>
To: Yahav Gindi Bar <g.b.yahav@gmail.com>
Cc: Galen Wright-Watson <ww.galen@gmail.com>, internals@lists.php.net
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable
Subject: Re: [PHP-DEV] Implicit isset in ternary operator
From: alex.aulbach@gmail.com (Alex Aulbach)

2012/7/24 Yahav Gindi Bar <g.b.yahav@gmail.com>:
> Yeah, that's a design decision, but its important because that's one of t=
he PHP greatest things - the code is very nice and readable, and it's kind =
of sad to ruin it...
>
> I didn't thought about template engines - I agree, it'll be great there, =
but does a language syntax need to be defined only for a specific cases lik=
e template engine?

It's one of the best things of PHP and the reason, why it was invented.

> If the programmers will follow your guidelines and use this operators onl=
y for some unique and rare cases - I strongly support that idea, but I'm af=
raid from programmers who'll make their program full of operators which mak=
es it unreadable by other programers...

Hhummm, every programming language could be written unreadable. Even
PHP. I can say that per sure. :)

> I think that operators overriding should be implemented in a class scope =
(only for object with object interaction, such as (merge operation): $merge=
dMember =3D $member1 + $member2; or for roles permission concat - $memberRu=
le =3D $adminRule - $editorRule)
> But that's a different topic from the suggested feature...

Which is a much better idea in general. My suggestion was only for a
very special context and should be easier to implement.

I currently think, this discussion needs more time, because I begin to
forget, for what this is really needed. :)

I suggest to (re)think about the real usage-cases...


--=20
Alex Aulbach