Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:114136 Return-Path: Delivered-To: mailing list internals@lists.php.net Received: (qmail 30773 invoked from network); 24 Apr 2021 19:40:34 -0000 Received: from unknown (HELO php-smtp4.php.net) (45.112.84.5) by pb1.pair.com with SMTP; 24 Apr 2021 19:40:34 -0000 Received: from php-smtp4.php.net (localhost [127.0.0.1]) by php-smtp4.php.net (Postfix) with ESMTP id 421FD1804C6 for ; Sat, 24 Apr 2021 12:44:11 -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-Virus: No X-Envelope-From: Received: from mail-lf1-f49.google.com (mail-lf1-f49.google.com [209.85.167.49]) (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 ; Sat, 24 Apr 2021 12:44:10 -0700 (PDT) Received: by mail-lf1-f49.google.com with SMTP id 4so22482567lfp.11 for ; Sat, 24 Apr 2021 12:44:10 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc; bh=jmZHH13Oz/2nN4+oBp5g/s8ai2f88LldbgjkNTB+Cjc=; b=P1cJfaCTLJbwOe0NibPh65APm7TLD4vRe4/jAE031yemph1xY8iMx8DUvweoxHujKX tc+MhrKuIBoCs4SKkhF82XNLd7/Cw2BoxewNZ+fUmOZkk7z8TbuJERfHZppNzIGxKEqq 88jKAWANXHMbm7ZKwNu0wsTEaGqb6FCRucg8JEPRhd6wEpzleKQOtWGitr7n863f3CER RbZydzRJlSHjMl6/OOebfADHkiSQO4IGqjUpVc6kz9422BCG9AJNPhjDMDG1bR4vJAUv mHySPgGpBhmVBkLrxTbaM99RzoZVMhEAa+k7XpZ6XUx+lMlIX5eXHdHN+u3E1aG3EMEA KGQA== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc; bh=jmZHH13Oz/2nN4+oBp5g/s8ai2f88LldbgjkNTB+Cjc=; b=drJAkEbkKshZNOcamX72zv3ixO/FEiYUj4reRxazp7vlv5JbAtAqW1Jd0nVTl+WcdC 09KM/uVq1xX5h2ucS4vd5wIwBLBRvX51eqijVBKgxtSbmRaFM0JoBlB0JH/5pP4O1pIO yv8/LnuRPkTyapQXE/NoHDDJ+nBSIbCA2zGARC2Gpo+yor/npqaAOetfBkubNzYnYOiw 4Xxxh0phYYxLt+CUFnXYyV0wE/+MwbTHIb9OcHoYACr7AcUe8z+ktTGYraY444oOSg2Z eofObAOmeMFPeqcuWg+w7hYzWftu+vLXAzPeF52Rb6/oo5aa4ckbkWjrgtwCvDI3N+nx A6dA== X-Gm-Message-State: AOAM532spBFzvTmaYsGbIenxKYT9kXNhx9hxOAC5RpGG16CGNpJhnavs tGPMIir5DxELf18DoxYYMbMLBaIJSUKwhrgORM4= X-Google-Smtp-Source: ABdhPJwnjJpYyIIiKjqCHVulZlaGpoxQiBMbXF/6m8X37x2lcnt6IMNJgoQwu4gCyS54SjqO2EuFt9uY+9Q4TLLtraU= X-Received: by 2002:a05:6512:b1a:: with SMTP id w26mr6797570lfu.418.1619293448186; Sat, 24 Apr 2021 12:44:08 -0700 (PDT) MIME-Version: 1.0 Received: by 2002:ab3:4e13:0:0:0:0:0 with HTTP; Sat, 24 Apr 2021 12:44:07 -0700 (PDT) In-Reply-To: <179049b1475.11134368b213512.254739612773841999@void.tn> References: <5b9f1500-615a-48f1-815f-1d48b327ef90@processus.org> <179049b1475.11134368b213512.254739612773841999@void.tn> Date: Sat, 24 Apr 2021 21:44:07 +0200 Message-ID: To: Saif Eddin Gmati Cc: Pierre , Saif Eddin Gmati , PHP Internals Content-Type: text/plain; charset="UTF-8" Subject: Re: [PHP-DEV] [RFC][Draft] Sealed Classes From: olleharstedt@gmail.com (=?UTF-8?Q?Olle_H=C3=A4rstedt?=) 2021-04-24 17:59 GMT+02:00, Saif Eddin Gmati : >> Doesn't this violate the principle: It should be possible to add new >> features without touching old code? > > This depends on which syntax is picked, both `for` and attribute syntax will > be completely BC. I'm not talking about BC, but the maintainability of the new feature itself. For the shape example, you'd need to edit the original file for each new shape you add, which is detrimental for maintainability and scalability. So what's a good use-case? Olle