Hi Matt,
Yes, that would stop people "possibly forget[ing] to set the request,
response, and other parameters", however, it would also mean closing
off the constructor completely and replacing it's initialisation
functionality with the init() method. All that is done because the
response and request objects are being set in
Zend_Controller_Action::__construct. Whether all this is a
particularly intuitive way of doing it is my question.
Would you (or other developers you can speak for) expect object
initialisation to be done in an init() method rather than the
constructor?
Nick
In other words it will need to be a warning. That is where I feel
that init() is unintuitive and most people (I say with hesitation
being a self elected representative) would expect to go with the
constructor for this task.
Why not declare Zend_Controller_Action::__construct() as final?
-Matt
