Stanislav Malyshev wrote:PJ>> No it is not. And this discussion (sorry) is going to be silly. We
PJ>> are not talking about such things but the ability to load a module at
PJ>> runtime.
Concepts of modules differ. PHP is built, more or less, so that you write in PHP using existing language facilities, and aren't supposed to change the facilities from PHP. That's why dl() is problematic - it violates this principle.
PJ>> I want to use an extension in a specific script/part that should not
PJ>> be available in other parts. A common usage. Or only for one host but
PJ>> not the other?
I don't really see a reason why somebody would want to enable GD to one vritual server while denying it to the rest. What's the point in it - you don't save anything?
For example, let's take a hosting company (mine). Suppose we decide to buy the last version of IRCG. We'd like to provide it only for some customers (the ones who will pay to have it).
So why not put them on separate servers, or put them through CGI if you don't care about performance? Or maybe implement access restrictions within IRCG?
Either way, what Andi said stands - fixing dl() means adding bloat, fixing and maintaining lots of bits and pieces of code in many different places, and it's something that we don't want to do, and said numerous times in the past that we have no intention of doing. In that sense, dl() is deprecated.
Zeev
-- PHP Internals - PHP Runtime Development Mailing List To unsubscribe, visit: http://www.php.net/unsub.php
