Re: [SMARTY-DEV] clear_compiled_tpl() bug or missing feature

As long as testing for template versions does not take a performance hit, I'd be for it. I wonder if we should integrate the version number into the template filename creation process. This way when you upgrade, new compiled files (and cache files) will get created. This leaves old versions of template files around, but does not add version testing logic. And of course, we should make the version value more granular so this is usable. Monte On Wed, 2003-11-05 at 22:33, Bharat Mediratta wrote: > From: "Thomas Schulz" <ths@4bconsult.de> > ... > > Is there a posibility to clear entire compile directory or maybe better to > > have grouped compile-ids with the same behavior of cache groups? > > While we're on the topic... It would be very helpful if Smarty > kept track of compiled template compatibility so that when the > framework changes such that old templates are no longer compatible, > I can discover this fact and clear out my compiled templates > without requiring my end users to take an extra upgrade step. > > I can't rely upon $_version since it doesn't have fine enough > granularity (eg, it was at "2.6.0-cvs" before and after the > core restructuring) and I integrate CVS snaps into my builds. > > I've been maintaining my own compatibility id, incrementing it > whenever I notice that things have changed, but I'm always > guessing and it'd be nice do it more officially :-) > > -Bharat