BM>> It is not a matter of the functions. If everything were a function or class BM>> ( like Java ) this would not be an issue. But, we have variables and such BM>> in these files that prevent us from be able to trust include_once.
Ah. Now I see what you mean. Then the solution would be or use classes, or make functions and variables different includes (since they are anyway different in the function context - former are global and later are not). BM>> And my fix will keep a function from being defined twice. It BM>> will simply also allow people who have become accustomed to BM>> using the language this way to keep doing it. I'm not sure that being allowed to use a language in a buggy way is a right thing to do... This would hide many "double include" errors, and would *not* restore the backwards compatibility - since code that didn't work then would work now with your patch. -- 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]
