Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:19823
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
To: James Crumpton <james@safesearching.com>
Cc: Greg Beaver <cellog@php.net>, internals@lists.php.net
In-Reply-To: <4363DB35.7080808@safesearching.com>
References: <4362C5F4.8090004@safesearching.com>
	<4e36d31d0510281847m3f54c70dy8b2a0679fa3c6cec@mail.gmail.com>
	<4362DFAB.1090701@safesearching.com> <43630958.4060406@php.net>
	<4363DB35.7080808@safesearching.com>
Content-Type: text/plain
Date: Sat, 29 Oct 2005 21:41:36 +0100
Message-ID: <1130618496.29279.6.camel@localhost.localdomain>
Mime-Version: 1.0
Content-Transfer-Encoding: 7bit
Subject: Re: [PHP-DEV] what happened to that new isset() like language
From: matthew@teh.ath.cx ("Matthew C. Kavanagh")

However, in terms of precedents, there are the combined assignment
operators such as &=, +=, .=, and so on. They would suggest that

$a ||= $b;

should be equivalent to

$a = $a || $b;

So I don't think ||= in the suggested usage is intuitive. And adding
strange automagical meanings to $a = $a || $b || $c; (and so forth)
shouldn't even be discussed by sane people ;)

On Sat, 2005-10-29 at 13:27 -0700, James Crumpton wrote:
> Regardless of what can be said about changing the behavior of '||', the 
> same isn't true for '||=', as it has no precedence in PHP.