Re: New zend_compile.c to solve all of the duplicate function problems

You asked me "why" twice, but I explained it in the email. Separating my last sentence to make it look like I think including files is a poor programming technique seems a little childish. So is asking "Why" over and over again when someone has already answered you. Lastly, I compared it to C because the developers write it in C and many aspects of it are modeled after C. Daniel ----- Original Message ----- From: "Stanislav Malyshev" <stas@zend.com> To: "Daniel Beckham" <danbeck@dealnews.com> Cc: "Brian Moon" <brianm@dealnews.com>; "PHP Development" <php-dev@lists.php.net> Sent: Friday, October 19, 2001 2:49 AM Subject: Re: [PHP-DEV] New zend_compile.c to solve all of the duplicate function problems > 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 > stas@zend.com http://www.zend.com/ +972-3-6139665 ext.115 > > > >