Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:110702 Return-Path: Delivered-To: mailing list internals@lists.php.net Received: (qmail 9602 invoked from network); 23 Jun 2020 09:43:15 -0000 Received: from unknown (HELO php-smtp4.php.net) (45.112.84.5) by pb1.pair.com with SMTP; 23 Jun 2020 09:43:15 -0000 Received: from php-smtp4.php.net (localhost [127.0.0.1]) by php-smtp4.php.net (Postfix) with ESMTP id 06F011804E4 for ; Tue, 23 Jun 2020 01:30:23 -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, RCVD_IN_DNSWL_NONE,RCVD_IN_MSPIKE_H2,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-yb1-f174.google.com (mail-yb1-f174.google.com [209.85.219.174]) (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 ; Tue, 23 Jun 2020 01:30:22 -0700 (PDT) Received: by mail-yb1-f174.google.com with SMTP id 187so10502172ybq.2 for ; Tue, 23 Jun 2020 01:30:22 -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 :content-transfer-encoding; bh=W9O8aP540s/giaoVanrk5Q9ANFjHI7krW2LyBnRVWvo=; b=XdDLuKNGlj6qKJuoPcG9Y1o/viBQb5+INNI3pr0PFSi/y5Cg7rYuK683asS6G0dzsz XaRyaqbI1XeJRl01bUnySP5TQFJzGQkVAwIt3jZSxNl7FjDTTtgf1B94NXjCVdh6/+pr DL9tmi+rCTcoFNVa6mdJQd0m3COHBwIX7+oTMRyHkbHCMhKCD7fMd+88/dkh70gRwLul u2peFedFf27ANXowRXWiWi/kQe+0FQOb9gKMDvFzEt2+RTIRm4ACQSbDqaHhy1TGFXBG JNfMpgnaIQr5XBOGoVviF/xmHAUm63Zim8ACcbTxzCVNftbtnhMrui0z6+AOoESJtGDM 8KjQ== 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:content-transfer-encoding; bh=W9O8aP540s/giaoVanrk5Q9ANFjHI7krW2LyBnRVWvo=; b=B41e9sBB/5u9gk9Cl21Dt/schkSxtZHtDZ+vU42rpxJeDFB9qmj4V2v3rrZAmdISRI 9qfVqIsrm5tO1J/F1kJodYSt87C+dfBGqGaLrrI309bfnus5GUR0JBmz9LG2IA7vKiRy jteY28ZiqmKEqsHfhhxK4vr4TYIEOP9faR07lAo39p+dC70KMpbR5EjcnLR3vxr3HScj jPT0MWPtnvXzBbaM9J6EKm8TFTluji23SMFTXZILoKUZ0EUwCgU+TGkL7dp5m6fGMLl5 YS+zILR7j/4Bjki40WCQ3O9fH1eGkbSCNhmhw2xIu5CllD6dDo/7n5gdpGwPem/NVlsU ZTBQ== X-Gm-Message-State: AOAM530zTW7iciRmDMLa/y/VfRFPZlBEJMHdg9+V1OMiqd0Uxw7ADFcF L2M0j/v9fCeEsxLMz+6C2EK0ymuQ1RoeMspBSm3wVGwA X-Google-Smtp-Source: ABdhPJxDGXPxX8olUnkiYulQO6uz0Arm8DnkvvDt5s2Xr5VRWiXq464ugz8IU/V9+J+Ox9tH37hkvvnZ+5+ymKhkuMs= X-Received: by 2002:a25:af93:: with SMTP id g19mr37196306ybh.109.1592901021581; Tue, 23 Jun 2020 01:30:21 -0700 (PDT) MIME-Version: 1.0 References: <37f1f8fb-0e1b-cc39-f4b6-6c943a731d49@telia.com> <250b7671-2919-9385-c149-931212397e4b@telia.com> <04d86e2d-0815-195a-6111-3034e0ca5918@telia.com> In-Reply-To: Date: Tue, 23 Jun 2020 10:30:10 +0200 Message-ID: To: PHP internals Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable Subject: Re: [PHP-DEV] Re: [RFC][DISCUSSION] Match expression v2 From: tovilo.ilija@gmail.com (Ilija Tovilo) Hi Bj=C3=B6rn >> I'd like to announce the match expression v2 RFC: >> https://wiki.php.net/rfc/match_expression_v2 > Absolutely so. I was thinking of the case mentioned in v1 RFC when it's u= sed > as a stand-alone expression. > match ($y) { > ... > }; > ` Optional? In this RFC the semicolon is required. Many people thought the grammar rules for the optional semicolon were confusing which is why I dropped that feature in this RFC. Ilija