Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:109533
MIME-Version: 1.0
References: <CAPyj-LB_RwOd7u02HipKb=iWuF-kMSr0=k=Ecd7eZFtxhz-GxQ@mail.gmail.com>
In-Reply-To: <CAPyj-LB_RwOd7u02HipKb=iWuF-kMSr0=k=Ecd7eZFtxhz-GxQ@mail.gmail.com>
Date: Sun, 5 Apr 2020 11:35:53 +0100
Message-ID: <CA+kxMuT_xdUvquseU9PXGuGxt6gY9F+kUaeVnK0BaS8zU+FWNw@mail.gmail.com>
To: Ilija Tovilo <tovilo.ilija@gmail.com>
Cc: PHP internals <internals@lists.php.net>
Content-Type: text/plain; charset="UTF-8"
Subject: Re: [PHP-DEV] [VOTE] throw expression
From: Danack@basereality.com (Dan Ackroyd)

Hi Iija,

During the discussion of the precedence, you wrote:

> There is a reasonable way to recognize this, namely to check if the expression
> after the throw keyword is of type ZEND_AST_OR or ZEND_AST_AND. The
> expression above will fail with this message (given that $condition is false):

Did the RFC get updated to address this?

As the current behaviour listed* in the RFC seems wrong and surprising to me.

cheers
Dan
Ack


* relevant part:

> $condition || throw new Exception('$condition must be truthy')
>  && $condition2 || throw new Exception('$condition2 must be truthy');
> // Evaluated as
> $condition || (throw new Exception('$condition must be truthy') && $condition2 || (throw new Exception('$condition2 must be truthy')));