Bug #40712 [Com]: return after "or"
| From: | someone dot wanted dot to dot be dot unknown at gmail dot com | Date: | Wed, 13 May 2015 15:49:12 +0000 |
| Subject: | Bug #40712 [Com]: return after "or" | ||
| References: | 1 | Groups: | php.bugs |
| Request: | Send a blank email to php-bugs+get-192653@lists.php.net to get a copy of this message | ||
Edit report at https://bugs.php.net/bug.php?id=40712&edit=1
ID: 40712
Comment by: someone dot wanted dot to dot be dot unknown at
gmail dot com
Reported by: s dot j dot t dot mocking at students dot uu dot nl
Summary: return after "or"
Status: Not a bug
Type: Bug
Package: *Programming Data Structures
Operating System: Linux (Debian Testing)
PHP Version: 5.2.1
Block user comment: N
Private report: N
New Comment:
In 2015, I'd like to ask php developers team make this feature available.
We can't write very clear code like
> <?php
> unlink() or return false;
Instead of that we forced to use huge if statement:
> <?php
> if (!unlink())
> return false;
I think community will be pleasant if we will see this feature implemented.
Previous Comments:
------------------------------------------------------------------------
[2007-03-04 04:09:31] iliaa@php.net
Thank you for taking the time to write to us, but this is not
a bug. Please double-check the documentation available at
http://www.php.net/manual/ and the instructions on how to
report
a bug at http://bugs.php.net/how-to-report.php
.
------------------------------------------------------------------------
[2007-03-03 18:54:25] s dot j dot t dot mocking at students dot uu dot nl
Description:
------------
"<statement> or die" works as expected, but "<statement> or return"
results in syntax errors.
Haven't found anything in the documentation which describes this behavior. If it's not a
bug, it's very counterintuitive.
Reproduce code:
---------------
This works:
function foo()
{
0 or die("bla");
}
This produces a syntax error:
function bar()
{
0 or return ("bla");
}
Expected result:
----------------
I would expect bar() to return bla
Actual result:
--------------
Parse error: syntax error, unexpected T_RETURN
------------------------------------------------------------------------
--
Edit this bug report at https://bugs.php.net/bug.php?id=40712&edit=1