Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:119897 Return-Path: Delivered-To: mailing list internals@lists.php.net Received: (qmail 38784 invoked from network); 11 Apr 2023 07:14:42 -0000 Received: from unknown (HELO php-smtp4.php.net) (45.112.84.5) by pb1.pair.com with SMTP; 11 Apr 2023 07:14:42 -0000 Received: from php-smtp4.php.net (localhost [127.0.0.1]) by php-smtp4.php.net (Postfix) with ESMTP id 7D17418005B for ; Tue, 11 Apr 2023 00:14:41 -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-yw1-f180.google.com (mail-yw1-f180.google.com [209.85.128.180]) (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 ; Tue, 11 Apr 2023 00:14:41 -0700 (PDT) Received: by mail-yw1-f180.google.com with SMTP id 00721157ae682-54bfa5e698eso295650777b3.13 for ; Tue, 11 Apr 2023 00:14:41 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20210112; t=1681197280; h=cc:to:subject:message-id:date:from:in-reply-to:references :mime-version:from:to:cc:subject:date:message-id:reply-to; bh=HVxzUDEq25kCgNyeNpmp0hPfPFCmIiJ1hvrl0wqgUB0=; b=WRjKZlcYrTkKRnHVuDyPo0EzNAs25SLVYGeeDEuN7UUiT5YhlLJtBXejp3lwxt5FcB 6QB0TFtLeMlW18acaf1vty5OnZzmuI0XWoemGAADYUH6eSDU1iKwt9R5UmA/G32jLAF0 vPSUo9UNN+3P9Fydc3OglgRYFGl3v3qhSCY4Ds6i1VcDeFLfmu1ns1NX746YxLu8+Zlo HsDoZX7Gmmb39u8md+DXyNK4xA0jsSR4b4YnAE6+uM03yyHLC/x59byoAee/ZY/zpYGS 6NYehmUpvxbyHQSA3PxkD8I/QcBCUd56xQ9/RCvvDtNsotAzple0CZwBOVQDODBtoYF1 0Y+g== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; t=1681197280; 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=HVxzUDEq25kCgNyeNpmp0hPfPFCmIiJ1hvrl0wqgUB0=; b=HzpKVGW8GrRTeTFoOiWtamZWP1MtPtSmFPb9HuFcyp3r5+GH7bz+/1QPAqHpPSST1O w7QvC7DNLRf1UCGXtaHqazmhyggAFYp+k5pPinzWjx1Kd4pcVvJ/u7qZZhkv9G+8Ck8r KU7uEWKmsyrMMC8GyfPJE+F366BSyUWxyS3OOdB6vcTWO6M1e/6FjVZDd4YzJm4UsMhy m2cm/OkyTFJR0t0LYtcohOCnO5zFXDC71i3ThstCEYBbxw2DJxVVP+XmzYfDlNAB4hTX 7XpO7LO8wWznWSk5RpPDprU9td3vEldIiBm0PUWwkR0+GFyPnvB5+KdMzuDi3VIpiYiU wi/Q== X-Gm-Message-State: AAQBX9eWBNI3mXyby4F2m3itYdyW+qUuqhf/REK6VMoaa3rfMO4PiXi3 0ZEk4Uev+SBCpIANiPGfqHVN5iG61UGfG74Qz6s= X-Google-Smtp-Source: AKy350aDICZDrI4pXkfsppm2rY6xLasJ3gE/CnZW5yeIcllYhODVBkI98Xf81AjkvJgsQYLS82DwV7OQu9UeNNFeQA4= X-Received: by 2002:a81:ac16:0:b0:54c:1fc7:c8d4 with SMTP id k22-20020a81ac16000000b0054c1fc7c8d4mr7077654ywh.10.1681197280346; Tue, 11 Apr 2023 00:14:40 -0700 (PDT) MIME-Version: 1.0 References: In-Reply-To: Date: Tue, 11 Apr 2023 09:14:29 +0200 Message-ID: To: "G. P. B." Cc: PHP internals Content-Type: multipart/alternative; boundary="000000000000b1491005f90a3ec7" Subject: Re: [PHP-DEV] [RFC] New core autoloading mechanism with support for function autoloading From: michal.brzuchalski@gmail.com (=?UTF-8?Q?Micha=C5=82_Marcin_Brzuchalski?=) --000000000000b1491005f90a3ec7 Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable Hi George and Dan, pon., 10 kwi 2023 o 14:17 G. P. B. napisa=C5=82(= a): > Hello Internals, > > Dan and I would like to propose a new core autoloading mechanism that fix= es > some minor design issues with the current class autoloading mechanism and > introduce a brand-new function autoloading mechanism: > https://wiki.php.net/rfc/core-autoloading > > The existing SPL autoloading functions would become aliases to the new Co= re > ones and will continue to work without any migrations needing to be > performed. > > Hope to hear your opinions about this! > > Best regards, > > George P. Banyard > Thanks for bringing this up, I like the RFC and addressing function autoload. Can we improve the RFC with a short description of issues on SPL autoload this RFC tries to address? It is mentioned in at least two places that this proposal addresses some minor issues with SPL autoload. However, I think it'd be worth mentioning them in RFC so the reader can get a complete picture of what the RFC tries to address besides adding new features like function autoload= . Cheers, Micha=C5=82 Marcin Brzuchalski --000000000000b1491005f90a3ec7--