Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:99392 Return-Path: Mailing-List: contact internals-help@lists.php.net; run by ezmlm Delivered-To: mailing list internals@lists.php.net Received: (qmail 87410 invoked from network); 6 Jun 2017 09:44:13 -0000 Received: from unknown (HELO lists.php.net) (127.0.0.1) by localhost with SMTP; 6 Jun 2017 09:44:13 -0000 Authentication-Results: pb1.pair.com smtp.mail=francois@tekwire.net; spf=softfail; sender-id=softfail Authentication-Results: pb1.pair.com header.from=francois@tekwire.net; sender-id=softfail Received-SPF: softfail (pb1.pair.com: domain tekwire.net does not designate 212.27.42.4 as permitted sender) X-PHP-List-Original-Sender: francois@tekwire.net X-Host-Fingerprint: 212.27.42.4 smtp4-g21.free.fr Received: from [212.27.42.4] ([212.27.42.4:12488] helo=smtp4-g21.free.fr) by pb1.pair.com (ecelerity 2.1.1.9-wez r(12769M)) with ESMTP id D6/3C-27119-C6976395 for ; Tue, 06 Jun 2017 05:44:13 -0400 Received: from [172.16.0.22] (unknown [158.255.108.131]) (Authenticated sender: flaupretre@free.fr) by smtp4-g21.free.fr (Postfix) with ESMTPSA id C8C2A19F5E7; Tue, 6 Jun 2017 11:44:06 +0200 (CEST) To: Fleshgrinder , php-internals References: <5313411f-40b4-58c6-83a8-7e813526f2a7@tekwire.net> <6a974b83-eb8b-8888-8dd2-fb4672a260f0@fleshgrinder.com> Message-ID: <0fdc7dae-e54e-3a10-a579-3b729eb5ed41@tekwire.net> Date: Tue, 6 Jun 2017 11:44:06 +0200 User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:52.0) Gecko/20100101 Thunderbird/52.1.1 MIME-Version: 1.0 In-Reply-To: <6a974b83-eb8b-8888-8dd2-fb4672a260f0@fleshgrinder.com> Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: 8bit Content-Language: fr Subject: Re: [PHP-DEV] Proposing inclusion of PCS in the 7.2 core distribution From: francois@tekwire.net (=?UTF-8?Q?Fran=c3=a7ois_Laupretre?=) Hi, Le 05/06/2017 à 21:26, Fleshgrinder a écrit : > I skimmed through the documentation of yours. There is however one > question left. Is it possible to have C code that is accessible only to > the PHP code of an extensions, instead of all user-level code? As extension PHP code is executed in the same context as user-level code, there is no way to have such access restriction. The workaround, IMO, would be to expose non-documented methods or functions. But nothing will prevent user-level code to call them. Regards François