Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:99548
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Received-SPF: pass (pb1.pair.com: domain rhsoft.net designates 91.118.73.15 as permitted sender)
To: internals@lists.php.net
References: <CALYT1YrCb_tLmj2hQZNnkPD-MbhdfRBYnWPyMsKv-A8c36-EMg@mail.gmail.com>
 <b005e591-843f-6b4a-fd1c-410e8ee4dc85@hoa-project.net>
Message-ID: <21f496b6-2af5-76e0-d8ca-9d49ab793258@rhsoft.net>
Date: Mon, 19 Jun 2017 16:28:45 +0200
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:52.0) Gecko/20100101
 Thunderbird/52.2.0
MIME-Version: 1.0
In-Reply-To: <b005e591-843f-6b4a-fd1c-410e8ee4dc85@hoa-project.net>
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Language: de-CH
Content-Transfer-Encoding: 8bit
Subject: Re: [PHP-DEV] [RFC] [Discussion] Retry functionality
From: lists@rhsoft.net ("lists@rhsoft.net")



Am 19.06.2017 um 16:24 schrieb Ivan Enderlin:
> Thank you for the RFC. I have a question though. I would like to know 
> how is it different from the `goto` language construction?
> 
> If I understand it correctly, both the following examples are identical:
> 
>     try {
> 
>          // …
> 
>     } catch (…) {
> 
>          retry;
> 
>     }
> 
> and:
> 
>     try {
> 
>     retry:
> 
>          // …
> 
>     } catch (…) {
> 
>          goto retry;
> 
>     }

even if both works the retry-statement is much clearer, especially when 
the code becomes larger than these few lines

> Also, what happens if the `try` block keeps failing over and over again: 
> This is a non-breakable loop.

well, as for other loops you are responsible at your own to count up a 
$retry_count and stop after N tries