Re: [SMARTY-DEV] Bug in Smarty Compiler concerning constants?
[email protected] (Oliver Jones)
| Newsgroups | php.smarty.dev |
|---|---|
| Organization | Deeper Design Limited |
| Message-ID | <[email protected]> |
On Mon, 2005-03-07 at 23:04 -0800, boots wrote:
> It looks like there is an issue but I believe that Smarty should output
> quoted text rather than a constant token, not? Especially since
> constants are accessed from the $smarty reserved variable, ie:
> $smarty.const.CONSTANT.
Erk. No. That would be annoying. Sure I can understand using
$smarty.const.CONSTANT etc when using the {$var} syntax as without a
prefix there would be no way of differentiating between function calls
and constants but that is just plain annoying (and unnecessary) in {if }
tags. Though understandable if you wanted a consistent API.
Personally I'm not a huge fan of the whole
$smarty.{section,const,capture} business.
Regads
--
Oliver Jones » Roving Code Warrior
[email protected] » +64 (21) 41 2238 » www.deeperdesign.com