Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:117872 Return-Path: Delivered-To: mailing list internals@lists.php.net Received: (qmail 32771 invoked from network); 8 Jun 2022 05:22:14 -0000 Received: from unknown (HELO php-smtp4.php.net) (45.112.84.5) by pb1.pair.com with SMTP; 8 Jun 2022 05:22:14 -0000 Received: from php-smtp4.php.net (localhost [127.0.0.1]) by php-smtp4.php.net (Postfix) with ESMTP id 53C261804F8 for ; Wed, 8 Jun 2022 00:08:10 -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,RCVD_IN_MSPIKE_H2,SPF_HELO_NONE,SPF_PASS, T_SCC_BODY_TEXT_LINE 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-f176.google.com (mail-yb1-f176.google.com [209.85.219.176]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange ECDHE (P-256) server-signature RSA-PSS (2048 bits) server-digest SHA256) (No client certificate requested) by php-smtp4.php.net (Postfix) with ESMTPS for ; Wed, 8 Jun 2022 00:08:06 -0700 (PDT) Received: by mail-yb1-f176.google.com with SMTP id a30so16234048ybj.3 for ; Wed, 08 Jun 2022 00:08:06 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20210112; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=rtaz5i8IGneMazYxxV55b5ltYh+sSW0X3KaaZxasVpY=; b=CuhOuUYuLnPLNe9IFj6p3i5AGCUry3ifYbTx5Ipo30K80ssiKGaFBNI7geXNaSmNpt QBPapR3AvvROvzMbxqk2DADPMgf2QaBU/BoOb7f59+NUKam4695hsRK1bnWJQUbtQ2/B eEIsbGe+c37WzvrLunCiW+0Hnt4Tk6w4Negqwl3y7BDFHnl2IhTjvEJXAm5fq74iFykm Vhk8OpO5lFtfwm9d62LHgr3yQ8YOP1wqgBF3ywFDrIKltVOel9DKnW15huFtbUu8Hxdr AMwtBE+PtbgwzDB+cqa6qf3RQ7f0X1f4QsyrA5VCaqwGHnkNmHF8nkIhkilA07pbbKX+ SJnQ== 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=rtaz5i8IGneMazYxxV55b5ltYh+sSW0X3KaaZxasVpY=; b=0e6rwYHa81svVKCv/KHExDA8+L6Lurm36K4OueHFyXo+xEsmShIc15N0AceuCOl8hI Gs7NHesmTEPmwl0UTbfjnEN0sVgNX2/aynrsm3mrGXi47FsDAvu06HWVaxKQrJZ1kT0T qeaSIa/rip7mCzEU/znMtrNY0D2PerQSVWr1kzD041aOJDfKnORHx0K9m0wmyN1ayvym YqqBCi9DiFnjqAGkmnKlQoG5d8eq/0QTEYZf/awCGHqxMZmEAiX1WGXAjR67zrIPzYC/ Ps5zgkRTbmVkfRnX6LojcGGkh4epEa016ragJ9ZkDnfvaPyB0G1IN63hKKeCcAqcu+I6 QdpQ== X-Gm-Message-State: AOAM531ooWCGYyBGN9JgA3eCltNFeWzjOytbk4kXDJCKL4o5QmJEiIiU jjzqloscq1d6q3r+QejXbrKInXUSq6p/PbuvQAo= X-Google-Smtp-Source: ABdhPJyTF2+NQWeLWebDomUIcZmQZm9MnVms4cfMu+ndW1D1aVumlQUrMzoKUkCV71Miok5gTc/dVX/RbDbm9ll0TMs= X-Received: by 2002:a25:2d0a:0:b0:663:e687:4e70 with SMTP id t10-20020a252d0a000000b00663e6874e70mr5581581ybt.559.1654672086031; Wed, 08 Jun 2022 00:08:06 -0700 (PDT) MIME-Version: 1.0 References: In-Reply-To: Date: Wed, 8 Jun 2022 09:07:53 +0200 Message-ID: To: CHU Zhaowei Cc: Sara Golemon , Robert Landers , shinji igarashi , Internals Content-Type: multipart/alternative; boundary="000000000000e8615e05e0ea5d35" Subject: Re: [PHP-DEV] Adding new closing tag =?> for keeping trailing newline From: ocramius@gmail.com (Marco Pivetta) --000000000000e8615e05e0ea5d35 Content-Type: text/plain; charset="UTF-8" On Wed, 8 Jun 2022, 08:15 CHU Zhaowei, wrote: > > > declare(ignore_newline_after_close_tag=false); // defaults to true, i.e > > existing behavior > > > This would avoid any new syntax rules, but still provide the ability for > > php-as-template-engine to behave in the user's preferred mode. > > I thought it's a consensus on internal that we should avoid such runtime > configuration that can affect code behaviour, otherwise we have a long list > to check when we debug or ask for help. Yeah I know we already have a lot, > and it's a easy and straightforward solution to add a switch for this kind > of issues, but we should be careful to introduce a new one. (Personlly I > was a supporter for runtime configuration as well, but I'm not able to > convince myself to ignore or defeat that argument.) > That would be a top-of-file `declare`, not a runtime configuration. > --000000000000e8615e05e0ea5d35--