Re: [SMARTY-DEV] smarty recompiling with op-code accelerators

That may help with Smarty upgrades, but does not address the original issue presented in this post. The accelerator op-code cache still won't refresh when the templates_c directory gets cleared (outside of a Smarty upgrade.) Mark Rogers wrote:

Monte writes:

Any thoughts on handling any of this a bit more gracefully? ;)

What would be the consequence of incorporating the Smarty version number into the hash which generates the compiled template filename? I can think of a few: it would fix this problem, and would stop systems breaking when Smarty was upgraded and compiled files not deleted (but at the expense of an ever accumulating templates_c directory). On balance (after 5 minutes of careful consideration :-) the benefits seem to outweigh the disadvantages, and I can't see that there'd be any noticable performance hit from doing this?