Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:9251 Return-Path: Mailing-List: contact internals-help@lists.php.net; run by ezmlm Delivered-To: mailing list internals@lists.php.net Received: (qmail 51402 invoked by uid 1010); 16 Apr 2004 09:32:30 -0000 Delivered-To: ezmlm-scan-internals@lists.php.net Delivered-To: ezmlm-internals@lists.php.net Received: (qmail 51364 invoked by uid 1007); 16 Apr 2004 09:32:30 -0000 Message-ID: <20040416093230.51363.qmail@pb1.pair.com> To: internals@lists.php.net Date: Fri, 16 Apr 2004 11:32:29 +0200 User-Agent: Mozilla Thunderbird 0.5 (X11/20040229) X-Accept-Language: en-us, en MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit X-Posted-By: 81.255.48.169 Subject: Feature proposal : php.ini option to disable access control and interfaces From: ganfset-php@dreams4net.com (Eric Daspet) Hi, Is it possible or planned to have a php.ini option in order to disable interfaces and access control ? something like assert.active for assertions. What I mean is something like a option "access_control.active". If it is disabled then PHP do not check private/public/protected access, do not load interfaces definitions with __autoload and do not use them. Could this speed up some script which have proven to be stable and correctly designed ? it should avoid loading some files (interface definitions) and avoid some checks (access controls). Am I right to think it may help performance ? and is this feature possible ? (probably not for 5.0 as we are in RC, but somewhere in future) Sincerely, -- Eric Daspet