|
|
Posted by Monte Ohrt on 08/11/05 22:25
I don't see a problem with custom delimiters. Myself, I use the
default... mainly because that is what we started with and have always
used, our clients use, etc. Custom delimiters would address the
{literal} tag issue, but that is probably it. The only downside I see is
adjusting third-party add-ons that are delimiter specific (such as
syntax highlighters, custom templates, etc.)
Maximillian Schwanekamp wrote:
> Does anyone have a good reason *not* to use custom delimiters? It
> seems like multiple character delims would make life a little easier,
> e.g. {{ and }}, avoiding having to use {literal} wherever JS or CSS
> code appears in a template. Obviously Smarty supports custom delims
> just fine, but I'm wondering if there's a significant reason that
> apparently almost everyone uses the default anyway?
Navigation:
[Reply to this message]
|