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

--- Mark Rogers <mark@quarella.co.uk> wrote: > IMHO we shouldn't really be telling the OS that the file hasn't > changed when > it has, which appears to be what we're doing here - presumably that > also has > implications for backups (if anyone is backing up templates_c, which > I'm > sure some people are), and doubtless other situations which (like the > op-code cache) aren't obvious until they bite. Should we instead be > looking > for a better way for Smarty to determine that the file matches the > template > and doesn't need recompiling? Again, its operational, isn't it? When "dumping" pre-compiled files from one server to another, instead of overwriting an existing templates_c dir, create a new one and have the application point to that one instead. No conflicts. I don't see why it should be Smarty's responsibility if timestamps (that were created elsewhere) are not consisitent on the local server or to determine the capabilities of the opcode caches, etc. xo boots