Move to SE problems

Verified.

$ php -r '1 && unset($var["a"]);'

is enough.

----------
[yohgaki@dev php-src]$ ./sapi/cli/php -v
PHP 5.5.0-dev (cli) (built: Mar 28 2012 17:33:51) (DEBUG)
Copyright (c) 1997-2012 The PHP Group
Zend Engine v2.4.0, Copyright (c) 1998-2012 Zend Technologies

[yohgaki@dev php-src]$ ./sapi/cli/php -r 'unset($var["a"]);'
[yohgaki@dev php-src]$ ./sapi/cli/php -r '1 && unset($var["a"]);'

Parse error: syntax error, unexpected 'unset' (T_UNSET) in Command line code on 
line 1
----------

Dmitry, could you review my patch for this bug plz?  thanks

oh, the patch is based on trunk.

unset() is like echo These are language constuct, Both of them are not 
expression in PHP, so code like this:

$c = 1 && echo 3;

IS NOT VALID script too;

Those language construct are "unticked_statement" @see 
Zend/zend_language_parser.y.
if,switch, do while and etc they all.

So from now on, This is not a bug.

Maybe we could make unset() a normal expression. I don't know how this decision 
made, maybe we can discuss it in maillist.

unset() is a statement, not an expression. So you obviously can't use it in an expression context. Changing buy type to Feature Request.

In my eyes the behavior *should not* be changed. unset() does not have a meaningful return value and as such should not be allowed in an expression context.

@nikic thinking of isset, include. :)

@nikic thinking of isset, include. :)

@nikic @reeze, after a deep thought,  I realize that I was wrong. yes, to fix this 
we should make unset return something.. 

so, mark it as a req , 
thanks

I didn't test the patch just made a quick review. I suppose it's incomplete. With patch it's possible to write $a = unset($b), but UNSET opcode doesn't care about return value, so what's going to be assigned to $a?

In any case, I think, such changes are not allowed in minor releases. So must not be committed into 5.4. Personally, I don't think it makes sense for trunk as well. It always possible to write

if (isset($entity['id'])) unset($entity['id']);

More clear, and just a few characters more :)

I just hit this bug trying to unset a variable in a for loop, like this:
<?php
for( ; ; unset($i)) {
    if($someCondition) {
        $i = 42;
    }
    if(isset($i)) {
        doSomething();
    } else {
        doSomethingElse();
    }
}

I understand why this currently fails and obviously there are workarounds, but intuitively unset should work in the third expression of a for loop.

No feedback was provided. The bug is being suspended because
we assume that you are no longer experiencing the problem.
If this is not the case and you are able to provide the
information that was requested earlier, please do so and
change the status of the bug back to "Open". Thank you.