Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:119851 Return-Path: Delivered-To: mailing list internals@lists.php.net Received: (qmail 12223 invoked from network); 10 Apr 2023 12:17:21 -0000 Received: from unknown (HELO php-smtp4.php.net) (45.112.84.5) by pb1.pair.com with SMTP; 10 Apr 2023 12:17:21 -0000 Received: from php-smtp4.php.net (localhost [127.0.0.1]) by php-smtp4.php.net (Postfix) with ESMTP id BAC1F180539 for ; Mon, 10 Apr 2023 05:17:17 -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.6 required=5.0 tests=BAYES_50,DKIM_SIGNED, DKIM_VALID,DKIM_VALID_AU,DKIM_VALID_EF,FREEMAIL_FROM,HTML_MESSAGE, RCVD_IN_DNSWL_NONE,RCVD_IN_MSPIKE_H3,RCVD_IN_MSPIKE_WL,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-pg1-f177.google.com (mail-pg1-f177.google.com [209.85.215.177]) (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, 10 Apr 2023 05:17:17 -0700 (PDT) Received: by mail-pg1-f177.google.com with SMTP id 41be03b00d2f7-5191796a483so232782a12.0 for ; Mon, 10 Apr 2023 05:17:17 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20210112; t=1681129036; h=to:subject:message-id:date:from:mime-version:from:to:cc:subject :date:message-id:reply-to; bh=1X+hf5eKr7MuVMtNZrDvxzF6xzXn+fdU1WSxjyt6PdY=; b=pfRUG9Pk9jD/qyzVg9Bv2+i4gIHYHdQ3V8ElDYlzBKNBkU9UdLOlgRnxiC8FmJ/93Z ifN7qtrLGnAfqK2kgCD2n3Ml3bXuVNiHq75UzUKiuQvCg9fX8nij7aZpvmYfGZHz52Zt 2IlK7nYLbbN5T1E3rYX21NVUIe/yd+gqsfgBsluKGxSToO9W74TwDJTlVIcmS2Qzk/q0 GlC2kUtYxGrJzNLuw53OxMU4701qwmzK4BpWhnYY5l3eJ5xMGnXHYovoi7z18JcUZGni aHnllHepcgf8D4FEiYbhPfi6RRHN9/C1NmcUrXZvGJJRSJzhFWBGd7Cp9hDRCWlzIPGL +Eiw== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; t=1681129036; h=to:subject:message-id:date:from:mime-version:x-gm-message-state :from:to:cc:subject:date:message-id:reply-to; bh=1X+hf5eKr7MuVMtNZrDvxzF6xzXn+fdU1WSxjyt6PdY=; b=FTxudxxGjU3SflcvVBHi+yLJDoTNlZ7J+te7omsEBv8a7k7im2HDUmCwNrKTrQ4amj /KjS0jhtErcgBmNCBCRZyJdvAuP0jhmzDWbiXgEK+rARV53IrUepjnujFxX3kt3w8eqv EvIVG1E+d5B8FGZIC4dcfyHHIWvnn0eXStbkHlWF0vmK7P7c12KVyYYbMHj2DOY6iMgS uRpztzj5Ai4T1R168XQRqKqfwFwjFMT44aUMwSIKmtjbdCVCp37AnLBht67T78mh2yFG B2a4ShkltqT57NryXSQjCNhnFT3C62AbaafjodAFXTvayDbq+FY3/VhDUIgB0cr1Idh/ d8ig== X-Gm-Message-State: AAQBX9cmKl3P752AIi4eYfeMJKP1tdNCe9nCp6tuuyyse3wDYSRh6qZY SULKMEzUYqTiiAnZWOnUGWAvrHNDzy+TQ0i10mkr8patSzg= X-Google-Smtp-Source: AKy350a3IX6Wyj5y5SfU69D+Uf2LUQXB8TcUKMmwl3ykTMFAVM74CaF7etlgwkpu+tKFTcZrjU7zOMnH9gS8J/U3sDw= X-Received: by 2002:a05:6a00:2d04:b0:62b:f8e9:2a17 with SMTP id fa4-20020a056a002d0400b0062bf8e92a17mr4751725pfb.3.1681129035760; Mon, 10 Apr 2023 05:17:15 -0700 (PDT) MIME-Version: 1.0 Date: Mon, 10 Apr 2023 13:17:04 +0100 Message-ID: To: PHP internals Content-Type: multipart/alternative; boundary="000000000000ff894505f8fa5a27" Subject: [PHP-DEV] [RFC] New core autoloading mechanism with support for function autoloading From: george.banyard@gmail.com ("G. P. B.") --000000000000ff894505f8fa5a27 Content-Type: text/plain; charset="UTF-8" Hello Internals, Dan and I would like to propose a new core autoloading mechanism that fixes 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 Core 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 --000000000000ff894505f8fa5a27--