Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:9252
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Message-ID: <5.1.0.14.2.20040416125435.02df8688@127.0.0.1>
Date: Fri, 16 Apr 2004 12:55:16 +0300
To: Eric Daspet <ganfset-php@dreams4net.com>,internals@lists.php.net
In-Reply-To: <20040416093230.51363.qmail@pb1.pair.com>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format=flowed
Subject: Re: [PHP-DEV] Feature proposal : php.ini option to disable
  access control and interfaces
From: andi@zend.com (Andi Gutmans)
References: <20040416093230.51363.qmail@pb1.pair.com>

Hi Eric,

I don't see very much value in such an option and I doubt it would help 
run-tme very much. In any case, the access control is very much part of the 
infrastructure and it can't just be skipped very easily.

Andi

At 11:32 AM 4/16/2004 +0200, Eric Daspet wrote:
>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
>
>--
>PHP Internals - PHP Runtime Development Mailing List
>To unsubscribe, visit: http://www.php.net/unsub.php