An earlier thread with the following subject makes some of our points: [PHP-DEV] Bug #13616 Updated: Compiler complains about function declaration after return is calle
Essentially, to answer your question. include_once() is a very poor way to write modular code that will be used across different projects and across different developers. You are placing the responsibility of not accidentally redefining function names on the user of the function library or code file and not on the file itself as it should be and as it is in other languages such as C. To put it shortly, it's a backwards way of including files and it's a poor programming technique. Daniel ----- Original Message ----- From: "Stanislav Malyshev" <[EMAIL PROTECTED]> To: "Brian Moon" <[EMAIL PROTECTED]> Cc: "PHP Development" <[EMAIL PROTECTED]> Sent: Thursday, October 18, 2001 10:14 AM Subject: Re: [PHP-DEV] New zend_compile.c to solve all of the duplicate function problems > BM>> See bug 13616. > > I see. I think you should really use include_once - I just do not see the > reason why not to do it and why patch the code instead. Could you explain? > > -- > 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] > > -- 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]
