Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:98176 Return-Path: Mailing-List: contact internals-help@lists.php.net; run by ezmlm Delivered-To: mailing list internals@lists.php.net Received: (qmail 63906 invoked from network); 4 Feb 2017 10:37:20 -0000 Received: from unknown (HELO lists.php.net) (127.0.0.1) by localhost with SMTP; 4 Feb 2017 10:37:20 -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 77.244.243.82 cause and error) X-PHP-List-Original-Sender: php@fleshgrinder.com X-Host-Fingerprint: 77.244.243.82 mx101.easyname.com Received: from [77.244.243.82] ([77.244.243.82:46738] helo=mx101.easyname.com) by pb1.pair.com (ecelerity 2.1.1.9-wez r(12769M)) with ESMTP id EC/12-38491-CDEA5985 for ; Sat, 04 Feb 2017 05:37:19 -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 1cZxiT-0008Mt-NC; Sat, 04 Feb 2017 10:37:13 +0000 Reply-To: internals@lists.php.net References: To: Scott Arciszewski , Nikita Popov Cc: PHP Internals , bowersbros@gmail.com, Niklas Keller Message-ID: Date: Sat, 4 Feb 2017 11:37:09 +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: 8bit X-DNSBL-PBLSPAMHAUS: YES Subject: Re: [PHP-DEV] [RFC] [VOTE] Libsodium as a core extension in PHP 7.2 From: php@fleshgrinder.com (Fleshgrinder) On 2/4/2017 12:54 AM, Scott Arciszewski wrote: > I like \Sodium\foo instead of sodium_foo, but it deviates from the norm.​ > ​ If we're going to break the norm, we should do so on a stronger majority > than 50%+1. > I see another problem besides the issue that a namespaced core elements are being introduced like in the US Senate, hidden within another bill, and the fact that I still don't like the Sodium API itself and that is that this might make autoloader updates in the future in regards to functions and/or constants more complicated. One idea back than was that the autoloader is only triggered for things that are listed in a use statement. This would have multiple advantages since we would not require any backslash in front of built-in stuff anymore as anything that is not within a use would never trigger the autoloader and remove any potential performance hit for built-in stuff due to autoloading. Sodium having its own namespace would definitely appear in use statements because that is how IDEs work today and because nobody wants to write `Sodium\foo()`, or do they? -- Richard "Fleshgrinder" Fussenegger