Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:116640 Return-Path: Delivered-To: mailing list internals@lists.php.net Received: (qmail 96307 invoked from network); 13 Dec 2021 10:38:36 -0000 Received: from unknown (HELO php-smtp4.php.net) (45.112.84.5) by pb1.pair.com with SMTP; 13 Dec 2021 10:38:36 -0000 Received: from php-smtp4.php.net (localhost [127.0.0.1]) by php-smtp4.php.net (Postfix) with ESMTP id B70F218054E for ; Mon, 13 Dec 2021 03:40:17 -0800 (PST) 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.3 required=5.0 tests=BAYES_50, FREEMAIL_FORGED_FROMDOMAIN,FREEMAIL_FROM,HEADER_FROM_DIFFERENT_DOMAINS, RCVD_IN_DNSWL_NONE,RCVD_IN_MSPIKE_H3,RCVD_IN_MSPIKE_WL,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-pj1-f48.google.com (mail-pj1-f48.google.com [209.85.216.48]) (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 Dec 2021 03:40:14 -0800 (PST) Received: by mail-pj1-f48.google.com with SMTP id p18-20020a17090ad31200b001a78bb52876so14434375pju.3 for ; Mon, 13 Dec 2021 03:40:14 -0800 (PST) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=bdhfQuEh1oEW3Ixrmkrts2/PvC3Nh2ZPyKcRpFehQA8=; b=U2Zyd/7gkA2SoCFX/30fNMj1G8421mYbwTbBY64A/u75us6q3im46gwzbszDOH6J8e W/mSNZfAQ5lE7l8/D+Bgnz0SXxEstgC/6uh4OWT0BhS3Qc3SV7oNxhZ5SfUOGC4iCAUJ dvA36n1jEGHkZs+LLivMqtSSq7YuHv0FfTKV3sMmSozIgeQS2vJNDEdKZI/4H5TrgaaS oq7Dsmy2gi6cHikydTLhpNVRtnh8OSORY6wHEjtNR6k0K8XAtpuvkLqL7+9SvP8kIZyY 84GEk864nTPFUpaynBonDeLHwFZoTSFKIYfMuwLtNqLFx/V74tESIWBE+LnvLrsquJlv pZjQ== X-Gm-Message-State: AOAM530LIERD0oqIPU86J+LiIF3EbcJGSGr8Lspv5HzNwUZEkxDobCKW 3xsQ8caLJKyMgAUCD2YeP5MmUyLT6yF1UFEu900= X-Google-Smtp-Source: ABdhPJy+14AnLGow1/fOOBYEOyCqxsrmIGf6p5QqzZeouPVYiCecIFcGdwwWMKEzBy3QzD/adKo7VnDV+6Y7Kl9fXVg= X-Received: by 2002:a17:902:a5c5:b0:143:c3cf:739b with SMTP id t5-20020a170902a5c500b00143c3cf739bmr94288643plq.9.1639395613153; Mon, 13 Dec 2021 03:40:13 -0800 (PST) MIME-Version: 1.0 References: In-Reply-To: Date: Mon, 13 Dec 2021 13:40:02 +0200 Message-ID: To: Oliver Nybroe Cc: Internals Content-Type: text/plain; charset="UTF-8" Subject: Re: [PHP-DEV] [RFC] !instanceof operator - reaction measuremen From: kalle@php.net (Kalle Sommer Nielsen) Den man. 13. dec. 2021 kl. 12.53 skrev Oliver Nybroe : > What do people think about this? Would love to clarify if needed. > > Best regards > Oliver Nybroe (he/him) I find this to be more a problem to be solved by individual coding standards and cs tools. The !instanceof syntax is awkward at best, at least I find it to be so because it is mixing a symbol with a word to form an operator. The documentation already states the following[1]: > Use of parentheses, even when not strictly necessary, can often increase readability of the code by making grouping explicit rather than relying on the implicit operator precedence and associativity. [1] https://www.php.net/manual/en/language.operators.precedence.php -- regards, Kalle Sommer Nielsen kalle@php.net