Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:98247 Return-Path: Mailing-List: contact internals-help@lists.php.net; run by ezmlm Delivered-To: mailing list internals@lists.php.net Received: (qmail 62578 invoked from network); 7 Feb 2017 17:30:45 -0000 Received: from unknown (HELO lists.php.net) (127.0.0.1) by localhost with SMTP; 7 Feb 2017 17:30:45 -0000 Authentication-Results: pb1.pair.com smtp.mail=php@fleshgrinder.com; spf=permerror; sender-id=unknown Authentication-Results: pb1.pair.com header.from=php@fleshgrinder.com; sender-id=unknown Received-SPF: error (pb1.pair.com: domain fleshgrinder.com from 212.232.28.122 cause and error) X-PHP-List-Original-Sender: php@fleshgrinder.com X-Host-Fingerprint: 212.232.28.122 mx201.easyname.com Received: from [212.232.28.122] ([212.232.28.122:38831] helo=mx201.easyname.com) by pb1.pair.com (ecelerity 2.1.1.9-wez r(12769M)) with ESMTP id 71/4B-03389-2440A985 for ; Tue, 07 Feb 2017 12:30:42 -0500 Received: from cable-81-173-135-7.netcologne.de ([81.173.135.7] helo=[192.168.178.20]) by mx.easyname.com with esmtpsa (TLS1.2:ECDHE_RSA_AES_128_GCM_SHA256:128) (Exim 4.84_2) (envelope-from ) id 1cb9bB-0006yJ-3R; Tue, 07 Feb 2017 17:30:38 +0000 Reply-To: internals@lists.php.net References: <459c6bef-8936-634a-9520-dbd65c35b7c7@fleshgrinder.com> <04295b76-3e0d-5ea3-7b4e-d07a15db4243@fleshgrinder.com> To: Niklas Keller , PHP Internals Message-ID: <561beaf1-7dc6-8f77-c7c0-240c49f2d5ca@fleshgrinder.com> Date: Tue, 7 Feb 2017 18:30:24 +0100 User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:45.0) Gecko/20100101 Thunderbird/45.7.0 MIME-Version: 1.0 In-Reply-To: Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-DNSBL-PBLSPAMHAUS: YES X-DNSBL-SURBL: YES Subject: Re: [PHP-DEV] Namespaces in Core From: php@fleshgrinder.com (Fleshgrinder) On 2/7/2017 11:39 AM, Niklas Keller wrote: > I don't see this as a potential problem. Autoloadeds are (1) not triggered > for already loaded symbols and (2) and more importantly, autoloaders > usually use a list of prefixes to load, so a whitelist, not a blacklist. > > Regards, Niklas > This is related to previous discussions about the implementation of auto-loaders for functions and constants where we it was always a problem on how to deal with stuff that has no use statement and no namespace prefix, e.g.: contains('foo'); In all cases, we know that the auto-loader does not require triggering because the references are not ambiguous and that is what this was about. -- Richard "Fleshgrinder" Fussenegger