RE: [SMARTY-DEV] clear_compiled_tpl() bug or missing feature
| From: | Eduardo | Date: | Fri, 07 Nov 2003 13:24:44 +0000 |
| Subject: | RE: [SMARTY-DEV] clear_compiled_tpl() bug or missing feature | ||
| References: | 1 | Groups: | php.smarty.dev |
| Request: | Send a blank email to php-smarty-dev+get-1919@lists.php.net to get a copy of this message | ||
Add 2 cents more, I think the same.
Jan's idea looks better but, is it really necessary?
-----Original Message-----
From: boots [mailto:jayboots@yahoo.com]
Sent: Friday, November 07, 2003 12:24 AM
To: Monte Ohrt; Bharat Mediratta
Cc: Smarty Dev
Subject: Re: [SMARTY-DEV] clear_compiled_tpl() bug or missing feature
Indeed, I don't much see the point of including this in Smarty, to be
honest. After all, only *one* version is expected to be used for a
given install, yes? Sure, upgrading requires a modicum of work--but you
can always script it or include it in your framework. I'd rather that
admin chores were kept as such lest Smarty try to do what it can not.
All-in-all, if an efficient method is found I'm not against it, but if
it is only protecting CVS cases (ie. distributions of Smarty code from
CVS, not release) then I think it does not merit consideration.
Just my 2c!
xo boots
__________________________________