Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:114347 Return-Path: Delivered-To: mailing list internals@lists.php.net Received: (qmail 20595 invoked from network); 10 May 2021 17:20:33 -0000 Received: from unknown (HELO php-smtp4.php.net) (45.112.84.5) by pb1.pair.com with SMTP; 10 May 2021 17:20:33 -0000 Received: from php-smtp4.php.net (localhost [127.0.0.1]) by php-smtp4.php.net (Postfix) with ESMTP id B991C1804BD for ; Mon, 10 May 2021 10:28:07 -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=1.4 required=5.0 tests=BAYES_00, HEADER_FROM_DIFFERENT_DOMAINS,HTML_MESSAGE,RCVD_IN_DNSWL_NONE, RCVD_IN_MSPIKE_H2,SPF_HELO_NONE,SPF_SOFTFAIL autolearn=no autolearn_force=no version=3.4.2 X-Spam-Virus: No X-Envelope-From: Received: from mail-lj1-f173.google.com (mail-lj1-f173.google.com [209.85.208.173]) (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, 10 May 2021 10:28:06 -0700 (PDT) Received: by mail-lj1-f173.google.com with SMTP id b7so21781945ljr.4 for ; Mon, 10 May 2021 10:28:06 -0700 (PDT) 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=5LeWJ+J7S7NNolcVM3fRE6MfsiTHe7htQxfrXN6GSFM=; b=jsEsYi17QdPFgUBJlwuWVVIGRVvoVta0e+bBoZeriFAf8pM9WvRpXXG5CdAi2akKKT tHMMZOboQ0ppJawxbZvtV+qvBBFWCBZwgbSSt6/1/yFXvP4GB7dxZr35SM6fWMTtCa5R FxxvAd+oxZ0Z046klrNToT1L4lbHEydWwWJ9KKANsoljNEms06MIhCM+f+stySrrH/oj sLIpaurxu6rZmXiE3kvxjl3y0biaCfts9goeXz0xJwG+USe9pfIT+Bl1rCPys61HZY1+ WjiwcOlZ/o8mRhxaUPWRLlH0BEOuWBKLnoHRiOxBN5s66HcUAyZMMQoVhgHfytJiAJLi 6G7w== X-Gm-Message-State: AOAM530gf9ngSTf6IodqMIqjDkZ7qazA+qhzHtebUro+IJRKcbZNrHne s+Fq6if5145QixiLO2V7C4Ht1dDZ1Xubh8apm1Teow== X-Google-Smtp-Source: ABdhPJz+tjGymEAGlPkl0JiD/YYazrENQV3azock5e73E1nHqmuFZleC3mW5VtUPfEhn0RNFHMOOoI4MZt1OPtWTmS8= X-Received: by 2002:a2e:a379:: with SMTP id i25mr21107372ljn.365.1620667682212; Mon, 10 May 2021 10:28:02 -0700 (PDT) MIME-Version: 1.0 References: <1620635361.9147.0@gmail.com> In-Reply-To: Date: Mon, 10 May 2021 12:27:51 -0500 Message-ID: To: Marco Pivetta Cc: =?UTF-8?Q?Mat=C4=ABss_Treinis?= , PHP Internals List Content-Type: multipart/alternative; boundary="0000000000007f5d5405c1fd1918" Subject: Re: [PHP-DEV] [RFC][Draft] Body-less __construct From: pollita@php.net (Sara Golemon) --0000000000007f5d5405c1fd1918 Content-Type: text/plain; charset="UTF-8" On Mon, May 10, 2021 at 3:56 AM Marco Pivetta wrote: > > Another point to be made here, as far as my interpretation of PSR-12, the > > curly braces occupy two lines for methods with multiline arguments. So > for > > whoever follows PSR-12, it's more like this, with brackets just dangling > > there across 2 lines. > > > > Given that: > > * `{}` can already represent what you want > * the issue is more of a coding-style related topic > > I suggest bringing this up in a new PSR instead. Consider that PSR-1, PSR-2 > and PSR-12 were designed pre-PHP-8, so they will need adjustments again, > but AFAIK nothing has moved yet, since the ecosystem is still adapting to > the PHP 8 changes (I myself haven't finished adopting it on many of my > libraries). > > A whole lot of agreeing with Marco here. The problem is the coding standard, not the syntax. Also, as Guilliam said in a later reply, using semicolon already has a meaning and this contradicts that. Let's not make the syntax more confusing purely to avoid updating a PSR that was meant to be a living standard. -Sara --0000000000007f5d5405c1fd1918--