Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:106349 Return-Path: Delivered-To: mailing list internals@lists.php.net Received: (qmail 4919 invoked from network); 30 Jul 2019 19:02:59 -0000 Received: from unknown (HELO localhost.localdomain) (76.75.200.58) by pb1.pair.com with SMTP; 30 Jul 2019 19:02:59 -0000 To: internals@lists.php.net References: <9ADC8994-9D3C-4810-A2DB-6FB81D513098@gmail.com> Date: Tue, 30 Jul 2019 17:27:56 +0100 User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:60.0) Gecko/20100101 Thunderbird/60.8.0 MIME-Version: 1.0 In-Reply-To: Content-Type: text/plain; charset=utf-8; format=flowed Content-Language: en-GB Content-Transfer-Encoding: 7bit X-Posted-By: 94.4.34.143 Subject: Re: [PHP-DEV] Re: [RFC] Namespace-scoped declares, again From: markyr@gmail.com (Mark Randall) Message-ID: On 30/07/2019 15:55, Rowan Collins wrote: > Yes, I was thinking of something more like Composer packages, rather than > like JS modules: code would mostly work as presently, but with some notion > of being "owned" by a particular package. This doesn't mean all the > functions of Composer would be integrated, but could provide richer > primitives, such as registering an autoload callback or preload list to a > particular package, rather than having to perform string matches. A slight tangent: At the point we're talking about composer integrating callbacks, preloading lists etc, isn't it about time that an spl_autoload_list was added that accepted the standard composer classmap [class_id => path] and forewent most autoload callbacks entirely? Mark Randall