Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:61938
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Received-SPF: pass (pb1.pair.com: domain gmail.com designates 209.85.213.170 as permitted sender)
MIME-Version: 1.0
In-Reply-To: <1708AB78DAB340DC8C8D7F54F652EBBF@gmail.com>
References: <CAOhuFvYD8FQw=xbK3hFqi4GYkOvCNzWjuhk2fqwBjKG9n2kuuQ@mail.gmail.com>
	<CAAyV7nEpp+Srxemgi913K2nZ7rztz6RV-9bNdXdPJx49q-AenQ@mail.gmail.com>
	<CA+Ky_uMV5nPmGZPktJ1a6XeYU68Zq=axbaZqMX0Te8D2CE9FGw@mail.gmail.com>
	<CA+Ky_uNs7tWy9AHma-1zgxKnNTdTe2FHqGm0Tmip9Awc=pqfAw@mail.gmail.com>
	<FE.FF.18983.B5BD9005@pb1.pair.com>
	<5009E557.1090906@sugarcrm.com>
	<1708AB78DAB340DC8C8D7F54F652EBBF@gmail.com>
Date: Wed, 1 Aug 2012 20:25:18 +0200
Message-ID: <CAKZjf5Sj8kZJtm5b_9-LP+bSDc2ci27szjtCZcQRY4=Wm_Z+Hg@mail.gmail.com>
To: Christoph Hochstrasser <christoph.hochstrasser@gmail.com>
Cc: Stas Malyshev <smalyshev@sugarcrm.com>, "Matthew Weier O'Phinney" <weierophinney@php.net>, 
	"internals@lists.php.net" <internals@lists.php.net>
Content-Type: text/plain; charset=ISO-8859-1
Subject: Re: [PHP-DEV] Implicit isset in ternary operator
From: alex.aulbach@gmail.com (Alex Aulbach)

2012/8/1 Christoph Hochstrasser <christoph.hochstrasser@gmail.com>:
> I'm lately using @$var["key"] a lot (despite it's slowness) and I like it a lot. It makes
> most code a lot more readable. I would be +1 for it, if we can make it fast.
>
> I think most people (me included) want only to avoid the notice for accessing undefined array offsets. What if we just remove the notice for accessing undefined array offsets, because it's the most common use case?

Getting philosophical. It's the same as if you want to read a page in
a book, but that page doesn't exist. For example a book with 40 pages,
but you want to read page 42. :) Is it an error to try it? Yes,
because if possible without error, you could do the same with the
universe and look at a part of it that doesn't exist. Someone has to
create it first. :)

More serious: For me it's the other way arround, it's one of the best
things, that have been introduced, because before it, a very small
write error had big impacts.

I see - as you - the need to make simple things more short, but
removing warnings from existing code constructs is definitly the wrong
way.

-- 
Alex Aulbach