Matthew Ratzloff wrote:
> Sorry, I deleted the other e-mail a little too fast, but this is in
> response to this:
>
>
http://www.akrabat.com/2006/05/13/zend_config-proposal-v2/>
> Two questions for the Zend team:
>
> - Why would you want to modify config information in memory?
In the proposal response, we asked that the constructor support an
optional flag to permit modification in memory. However, the flag can't
be changed after instantiation (to lock read-only mode). This is to
allow for easier testing of components using Zend_Config.
> - Why no nested "extends"?
We want to discourage spaghetti files.
Mike