Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:119273 Return-Path: Delivered-To: mailing list internals@lists.php.net Received: (qmail 45052 invoked from network); 16 Jan 2023 12:38:40 -0000 Received: from unknown (HELO php-smtp4.php.net) (45.112.84.5) by pb1.pair.com with SMTP; 16 Jan 2023 12:38:40 -0000 Received: from php-smtp4.php.net (localhost [127.0.0.1]) by php-smtp4.php.net (Postfix) with ESMTP id 71A981804A9 for ; Mon, 16 Jan 2023 04:38:40 -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=0.0 required=5.0 tests=BAYES_40,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-yb1-f181.google.com (mail-yb1-f181.google.com [209.85.219.181]) (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 ; Mon, 16 Jan 2023 04:38:34 -0800 (PST) Received: by mail-yb1-f181.google.com with SMTP id t15so30108887ybq.4 for ; Mon, 16 Jan 2023 04:38:34 -0800 (PST) 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:message-id:reply-to; bh=h3rQiyq/T+PtN30PeH7uMNHc/tU9VjBE4+X/qEdaLZE=; b=jMiDH4zO/4Ahd2CRJrs74pkuVA5W54EX3EzvvTJPS9xxswKGVB85d5Chiz3hVGqEtL 52jp8P9/Q4j5f/vYdvLdxjb/wbhsrIouubUK/iMBRGuZ7/6uaLT23Jr+wFqtKqwesahI iu6c+dSBKnREKj7SMaKrFVEyRBXfr6BwERUEctr3UG69PNiVJlF4SxaoT1CZD564R6Z5 FwxElQ8JxSXxm6xHSi9HkrWVtVDHkUe55jQnwNsX1MHioF05QmD4em7F1azBgdMBq6y9 ycvyDGLEYURAElDi1IqE2PiPeYvNbG2TApy83CLOzq2bKo1Fkywdq7vmPMIi3BWk97o4 yf7w== 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:message-id :reply-to; bh=h3rQiyq/T+PtN30PeH7uMNHc/tU9VjBE4+X/qEdaLZE=; b=rVL1TqdqsM+4G9Jl4SkqBKNVjhuTeLM0H/P1PF/487eTmse1+LqwwKfSN0GJqdXFK5 Vahjx3vsiZ4XJCwLAGWAlQcnX17s3WDkrY6I2KTC2OqJKQBgchTp38VlOTHdK8qd5dh1 U/gvNpfMYfb51K7syaewHS+FFF4YUGgCwZkhoERAhZ06Xi2InSm6UcBZ0Jk3yh3c8ckK ofJcUBLnpaYSo7lJXZjA7IWG4bkYlTLmLlS9ogN/0FgXQyqCcm0jeq/ewxuLC8ACHSYG /EjhlwkFxj5gTMYcUZLcTihlUwzB0e3ESxu8hoBQ44w1ZHT6mB4x5Lo6P9TK443EZnH0 PwjQ== X-Gm-Message-State: AFqh2koDton+SFOibFtvoOD5GhhFrJXsohTMvEbgNtZVdTHb/cIu6l02 wGfTvxIZCIiKJpyN4jl8EGkap5xcr/LdNyY6oCM= X-Google-Smtp-Source: AMrXdXsaI8cVTJ3PfNjJxtkVf5RsKV44V8Djl+L3ljVpSem9BkiPtpGqVb+oaBUvPx82S+PFC4d/wvVJpcDoc5jtmXE= X-Received: by 2002:a25:bc83:0:b0:7ec:2e1a:c914 with SMTP id e3-20020a25bc83000000b007ec2e1ac914mr17600ybk.258.1673872713284; Mon, 16 Jan 2023 04:38:33 -0800 (PST) MIME-Version: 1.0 References: In-Reply-To: Date: Mon, 16 Jan 2023 12:38:24 +0000 Message-ID: To: Max Kellermann Cc: internals@lists.php.net Content-Type: multipart/alternative; boundary="0000000000007981ac05f260dc4b" Subject: Re: [PHP-DEV] RFC: rules for #include directives From: tekiela246@gmail.com (Kamil Tekiela) --0000000000007981ac05f260dc4b Content-Type: text/plain; charset="UTF-8" Hi, Did you create an RFC already? Or is this RFC-like discussion? In either case, if you are asking community to come to a decision, we need to see some background. Why do you want to change this? What's the benefit? What's the impact on other maintainers, especially extension maintainers? Do you see any downsides to your new approach? Regards, Kamil --0000000000007981ac05f260dc4b--