Re: [PEPr] +1 for HTML::Template_Savant
| From: | Greg Beaver | Date: | Wed, 09 Jun 2004 12:34:03 +0000 |
| Subject: | Re: [PEPr] +1 for HTML::Template_Savant | ||
| References: | 1 2 3 4 5 | Groups: | php.pear.dev |
| Request: | Send a blank email to pear-dev+get-30277@lists.php.net to get a copy of this message | ||
Alan Knowles wrote:
I'm pretty sure it isn't :). I will take a look at the design, there may be a way to determine the presence of errors without even including ErrorStack.php, which would be ideal.{ $this->err =& new PEAR_ErrorStack(); }function Template()Greg may be able to expand on this, but is it required to initialize PEAR_ErrorStack even if it's never used.?? I would presume not..??
The two approaches are: a) extend all engines of a core Interface, with some limited implementation in it.. b) Provide a core Class that implements (or loads as required) the features required by all templates. I'd tend to go with B) asB is exactly what I meant by my conditional vote for Savant. Required features must be in the base class, otherwise you get code duplication, with greater potential for bugs, etc Glad to see you two working together, this is fantastic :). My only request is I would like to make sure that the core implementation does not require all unneeded features to be installed, but has the ability to error out (exception if you really want) if a feature is not installed, so that a minimal install is not only possible, but built into the design capabilities. Greg