RL>> Stanislav, he does have a point in that it would be a good idea to be able RL>> to create an include file which protected itself from multiple exclusion RL>> instead of relying on the user to use the file correctly. That's what he
I'm these minutes finish to write a proposal which is meant to adress some part of this issue. I will post it very soon. RL>> which is which is not great. It would be nice if you could trigger the RL>> include_once functionality from the file being included. I fear this won't sit well with how the engine works... But maybe you won't need this, in fact. I think that this should be done in more systematic way, so that if you include some code bunch, you are sure this and that is defined, without checking each thing by itself. Especially when we talk about functions and classes, which are not the same small change as variables and should be handled more systematically. There still be the cases when you do need such hacks, in one way or another, but I think that a systematic approach to the problem will do better than a hackish 'patch there, fiddle here' approach. -- 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]
