Re: [SMARTY-DEV] current vs past version

Ahhhhhhhhhhhhhh, the light bulb comes on! Instead of using 'eval()' which has lots of limitations and is slow, Smarty uses include()! that's ........... smart! messju mohr wrote:

On Fri, Aug 15, 2003 at 06:30:38PM -0700, Dennis Gearon wrote:

I'm using an older version 2.4.2 I have 'caching' disabled, And even if I set 'force_compile', smarty still writes the cache to disk. Why?

you mean "compiling". "caching" is something different in smarty lingo.

What is the point?

smarty uses php's include() to render the template (when doing display() or fetch() )

My reason for wanting to do this is that I don't yet have permissions set up for smarty to write to a directory, since I'm on a shared host, just haven't asked the sysop.

then make your host provide you a directory for it.

There might even be applications that the developer doesn't want the time it takes to write to the disk, but is willing to take the hit for compiling everytime.

this makes only sense for stuff displayed a few times. smarty is designed for rendering *templates*, this means for stuff displayed many times.

Now the part concerning the current/future version. Does it/is is planned to NOT write the disk if not caching?

to my knowledge: no, this is not planned. the discussion comes up every few month. a related faq entry is: http://smarty.incutio.com/?page=SmartyFrequentlyAskedQuestions#project-4 greetings messju