DB>> I do not know Java. In Perl, namespaces exist, so it's a DB>> completely different ballgame. But even still, it's not the DB>> responsibility of the user to know the inner workings of a DB>> module or package in Perl.
If we talking about "how to quick hack PHP engine so that it would suit this-minute needs of someone" - it is not so interesting to me to discuss. If we talk about PHP strategy - it's already accepted that PHP needs namespaces, and there's a work in progress on it, so it's not "completely different ballgame". DB>> function library from the user themselves. Why are you DB>> continuing this argument? Mostly because I have got tens of answers to this thread and only *one single answer* on my package proposal. So if this thread is the place where my voice is heard - I will use it :) -- Stanislav Malyshev, Zend Products Engineer [EMAIL PROTECTED] http://www.zend.com/ +972-3-6139665 ext.115 -- PHP Development Mailing List <http://www.php.net/> To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] To contact the list administrators, e-mail: [EMAIL PROTECTED]
