Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:118547 Return-Path: Delivered-To: mailing list internals@lists.php.net Received: (qmail 51602 invoked from network); 31 Aug 2022 21:13:51 -0000 Received: from unknown (HELO php-smtp4.php.net) (45.112.84.5) by pb1.pair.com with SMTP; 31 Aug 2022 21:13:51 -0000 Received: from php-smtp4.php.net (localhost [127.0.0.1]) by php-smtp4.php.net (Postfix) with ESMTP id 2DD101804D0 for ; Wed, 31 Aug 2022 14:13:51 -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=0.0 required=5.0 tests=BAYES_20,DKIM_SIGNED, DKIM_VALID,DKIM_VALID_AU,DKIM_VALID_EF,FREEMAIL_ENVFROM_END_DIGIT, 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-ed1-f44.google.com (mail-ed1-f44.google.com [209.85.208.44]) (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, 31 Aug 2022 14:13:50 -0700 (PDT) Received: by mail-ed1-f44.google.com with SMTP id b16so20037360edd.4 for ; Wed, 31 Aug 2022 14:13:50 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20210112; h=cc:to:subject:message-id:date:from:in-reply-to:references :mime-version:from:to:cc:subject:date; bh=nyDlN/39lsmgvSqoBG6jeLjemiOpZqlvgZKaPYeMKO0=; b=H9pRbZgkkT22ocxE1qyamr8asCSRo03o73X2B/4mYeFTbQWPKzz2XeLcmXp7kN50On Nth8vbhaWwH6XC4XRwZNmlCwbqkj7iD5FF+iQB4bgY5T8encfD/WtdNfVV51jEo6fdi5 sCB5P8oUuNqshgxEC767pG28KzOEgrpPhNFYEctY3Fn2evFlxEAYkEmiYF5CjNieYhGP 0hSqkF76vLFiSU9uATZqdLELbQ6wL5aSMIifNlOiIQ7Bmog0P2XKTTHl8Ob2qaQ5RLtK P1DXpcgn8alnQiosXEccZA3Qj/tlZeQOkyavUU2y2cfCvdnKrRA04DsC9UolW/NOYGhx sTXQ== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=cc:to:subject:message-id:date:from:in-reply-to:references :mime-version:x-gm-message-state:from:to:cc:subject:date; bh=nyDlN/39lsmgvSqoBG6jeLjemiOpZqlvgZKaPYeMKO0=; b=wjuBPjYLQ3n42g18eIkU8oTeWrQwCR7TLqTtjyGhu0ApvK353zHTSjDTaZyVMEiuG7 3J+rT89sq/JJ10titBzYnXOqoKzVeX53Wk7O1oRvjt13xRx35DmORe+7x35noTnOw/D8 qbEnR2UQ0XTz04m9uknBmQS3UVYesSO48K0D5MPMi560S00okWLjqmqmXlQx4k8taaSG LxdSQby3m3PmkBh3KAxlZwkAHTChgn6Ro5Q4QzlVlWyO9Xz7c/L0uzzgmUOy5UB2MYae UlxtCrKIOhk1AU30Y4DKjqTG/hLoOBnZDNM/9b43sYmQYieOYjoCjfIA0+oV/jheeThM LqcA== X-Gm-Message-State: ACgBeo2ofs6thFPGS7Qzbiz7eZ1I3cNLAdwaqLzPAhHBZOxbbJdKdIds ZnlxnPvGWDpHy+CK1kGq7AVs/kWsVSHv/Y1OEFYda1u8 X-Google-Smtp-Source: AA6agR4UjuuaTgGEEva/XWesy0lGSEMkfzQK2Zbr2qqTZLNClwbnFQH5GGLYH40NLMs4X/oswwxbLSUcntJbgPrnxgE= X-Received: by 2002:a05:6402:ea1:b0:443:d90a:5d31 with SMTP id h33-20020a0564020ea100b00443d90a5d31mr26648740eda.121.1661980428604; Wed, 31 Aug 2022 14:13:48 -0700 (PDT) MIME-Version: 1.0 References: <00d044c6-8059-3487-ca3a-7881d4ca462a@gmx.de> In-Reply-To: Date: Wed, 31 Aug 2022 23:13:31 +0200 Message-ID: To: Sara Golemon Cc: "Christoph M. Becker" , PHP internals Content-Type: multipart/alternative; boundary="000000000000121c1b05e78ff94d" Subject: Re: [PHP-DEV] No longer allow block mode for declare(encoding) From: divinity76@gmail.com (Hans Henrik Bergan) --000000000000121c1b05e78ff94d Content-Type: text/plain; charset="UTF-8" >it might be hard to properly implement support No effort should be wasted supporting this. +1 On Wed, Aug 31, 2022, 21:21 Sara Golemon wrote: > On Wed, Aug 31, 2022 at 10:43 AM Christoph M. Becker > wrote: > > > recently, there was a bug report regarding declare(encoding)[1]. I've > > checked that, and found that the current implementation of > > declare(encoding) doesn't make sense regarding "block mode", since this > > is completely ignored; instead, each (allowed) declare(encoding) works > > from where it is written till the next declare(encoding) (well, probably > > more or less). > > > > Since I consider switching the character encoding in the middle of a > > file not reasonable (and it might be hard to properly implement support > > for that), I suggest to disallow block mode for declare(encoding) as of > > PHP 8.3. A respective PR is available[2]. > > > > > I think I can imagine scenarios where switching encodings within a file > would.... work? Especially for ASCII transparent encodings... That said, > if you're currently depending on multiple encodings in a single file then > you probably deserve whatever you get. > > +1 > > -Sara > --000000000000121c1b05e78ff94d--