DB>> Essentially, to answer your question. include_once() is a very DB>> poor way to write modular code that will be used across DB>> different projects and across different developers. You are
Why? DB>> placing the responsibility of not accidentally redefining DB>> function names on the user of the function library or code file DB>> and not on the file itself as it should be and as it is in other DB>> languages such as C. To put it shortly, it's a backwards way of PHP is not C. So PHP can not be "such as C". You are placing responcibility of including a module onto the engine, and that is completely OK with me. I agree that it would be good to have more developed concept of a package and all the hoopla that is going with that - but until then, I see nothing wrong in include_once. DB>> including files and it's a poor programming technique. Why? -- 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]
