Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:109609 Return-Path: Delivered-To: mailing list internals@lists.php.net Received: (qmail 42053 invoked from network); 13 Apr 2020 18:31:58 -0000 Received: from unknown (HELO php-smtp4.php.net) (45.112.84.5) by pb1.pair.com with SMTP; 13 Apr 2020 18:31:58 -0000 Received: from php-smtp4.php.net (localhost [127.0.0.1]) by php-smtp4.php.net (Postfix) with ESMTP id 3D0F418058E for ; Mon, 13 Apr 2020 10:01:25 -0700 (PDT) X-Spam-Checker-Version: SpamAssassin 3.4.2 (2018-09-13) on php-smtp4.php.net X-Spam-Level: X-Spam-Status: No, score=-2.1 required=5.0 tests=BAYES_00,DKIM_SIGNED, DKIM_VALID,DKIM_VALID_AU,DKIM_VALID_EF,FREEMAIL_FROM,HTML_MESSAGE, RCVD_IN_DNSWL_NONE,SPF_HELO_NONE,SPF_PASS autolearn=no autolearn_force=no version=3.4.2 X-Spam-ASN: AS15169 209.85.128.0/17 X-Spam-Virus: No X-Envelope-From: Received: from mail-oi1-f181.google.com (mail-oi1-f181.google.com [209.85.167.181]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange ECDHE (P-256) server-signature RSA-PSS (4096 bits) server-digest SHA256) (No client certificate requested) by php-smtp4.php.net (Postfix) with ESMTPS for ; Mon, 13 Apr 2020 10:01:24 -0700 (PDT) Received: by mail-oi1-f181.google.com with SMTP id k133so7207207oih.12 for ; Mon, 13 Apr 2020 10:01:24 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=Is6EmMHvSxtzolKqnYRIDKZjma+o6GYXvNj/EQuI+/Y=; b=skb1CqydBLWafOhxZEYYzam9rj0mT6yDvAExHEclIau2yCb/vDYx4nv9BLk5nAB9/X b2/FJ+b061/f/CLwWKN3dBVPBEPSjM0SgbEYzHt2qMdBDnw4hfI8kvAq3JLz88wrS0by qfPcso9sSmBH3HmI1Gqmh1b0ZAWj5yQXhV8JIdiCF4QdXJwyr7+3YhHxdnT61+oeZeQ4 erB5SNDG5gaOPjJn0fHZ7gb4FkodWkjHwDKo1xmX7wHIT2fddNtFaIWcyqrQ7L7+qqjm UCQwSKBv5BUQLBPuFv6F4s8bZB2wV7d8Sl1PweP5ZSkD8O8W/hC0eVl9lFi94geW2Xd/ Uw7w== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=Is6EmMHvSxtzolKqnYRIDKZjma+o6GYXvNj/EQuI+/Y=; b=LYEKYS4rYhoNhNA/cYTyBTfFBcQlL6HOdFZknR537pEXjl54xnbwFpWgJp1WT8gAoT SACBmEPOHtIcwwzNXVFaQ6UzrwlK2VANVPg6KgJvh9zaoRT6hnvYRpD+16CS5tgRCNYk xsGd3exSg0jBH1FQbPS9mADHrvsaO0EcCrmpl5TYBUeUK/xK/k/IhMAPOQF4X3Wl2W3P yOvSP1hQcVLNK5TUPQYAuepm8nhBcAryacRQd32qUTJFok2g9ZnF0kknIXHRuceZ6uk8 GDKx4y8K5us34v9/KIH8Bf5LoSeQh+wcL5CwyIAyti8in0ImL5QCLtzYTb0u4DFh/K0E 2ckw== X-Gm-Message-State: AGi0PuYWMywjZ0F0QY0TopIitgpM05L0WNnaot5Kh8cg2OU6j6jeimJb tJRgSr/h5PQmrnC2SgW9XchpTzhiIyJ/GWFLitv3IfbS X-Google-Smtp-Source: APiQypLFhOy4xteESbXP+y/mMmn61tmgXWh1g0o6ipzCpFom5qCPrT1i11MdiHu4PBItIi4hiUUBT2LrU6wUstTwVDs= X-Received: by 2002:aca:cf0d:: with SMTP id f13mr12020633oig.162.1586797283108; Mon, 13 Apr 2020 10:01:23 -0700 (PDT) MIME-Version: 1.0 References: <6aebe21d-2137-885e-5ee9-99d4f917a7f9@gmail.com> <5071DCCE-4572-4B1F-A50B-832C5EA74795@gmail.com> In-Reply-To: Date: Mon, 13 Apr 2020 14:01:11 -0300 Message-ID: To: Reindl Harald Cc: PHP internals Content-Type: multipart/alternative; boundary="00000000000063ea6405a32f0882" Subject: Re: [PHP-DEV] [DISCUSSION] Match expression From: david.proweb@gmail.com (David Rodrigues) --00000000000063ea6405a32f0882 Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable But when we do: function x() { $a =3D function () { return 123; } } We know that "return" here is for the current function () scope, and not for the parents one. So "return" inside inlined-switch should be used to specify the switch return itself. Seems clear to me. Atenciosamente, David Rodrigues Em seg., 13 de abr. de 2020 =C3=A0s 12:32, Reindl Harald escreveu: > > > Am 13.04.20 um 17:08 schrieb David Rodrigues: > > With all the humility of the world and without wanting to be exhaustive > > about this, my only question is why can't we keep it as a switch, inste= ad > > of creating a new keyword? > > > > $x =3D switch ($y) { > > case 0: return 1; > > case 1: return 20; > > // default: return null; > > }; > > because when someone changes behavior where return is expected to return > from a function/method someone could break his fingers? > > return means "stop function or include" and not "stop switch statement" > --00000000000063ea6405a32f0882--