Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:130052
Message-ID: <a9c192e6-964c-4d85-a810-7df495662649@varteg.nz>
Date: Sun, 8 Feb 2026 11:51:20 +1300
Precedence: list
MIME-Version: 1.0
User-Agent: Mozilla Thunderbird
Subject: Re: [PHP-DEV] Return expression
To: internals@lists.php.net
References: <bfcfa113-01cd-42d8-923e-edc896c6b548@varteg.nz>
 <CAPyj-LBojf+UpD7bz=9Gr-MN=cQzpS5Njnqn5_ccFXBg22tixQ@mail.gmail.com>
Content-Language: en-GB
In-Reply-To: <CAPyj-LBojf+UpD7bz=9Gr-MN=cQzpS5Njnqn5_ccFXBg22tixQ@mail.gmail.com>
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 7bit
From: Weedpacket@varteg.nz (Morgan)

Sorry; thought I'd acknowledged this already.

On 2026-02-03 05:00, Ilija Tovilo wrote:
> 
> I encountered similar issues for block expressions, for which
> { return; } is effectively equivalent to return. I explained the
> problem in more detail here:
> 
> https://wiki.php.net/rfc/match_blocks#technical_implications_of_control_statements
> 
> Ilija

Thank you for that. If abandoning a function mid-statement can leave 
things dangling then that's a big no-no. I suppose exceptions can get 
away with it because there's an opportunity to clean up danglers left by 
the (possibly multiple) abandoned functions if and when they're caught 
or while the stack's being unwound.