Re: [SMARTY-DEV] tokens as input to modifiers
| From: | messju mohr | Date: | Thu, 08 Jul 2004 07:41:39 +0000 |
| Subject: | Re: [SMARTY-DEV] tokens as input to modifiers | ||
| References: | 1 2 | Groups: | php.smarty.dev |
| Request: | Send a blank email to php-smarty-dev+get-2458@lists.php.net to get a copy of this message | ||
On Wed, Jul 07, 2004 at 03:44:20PM -0700, boots wrote:
> > --- messju mohr <messju@lammfellpuschen.de> wrote:
> > > i think it's intended. "null" or "true" could be registered
> > > functions which makes the above valid syntax. allowing "null" and
> > > "true" as constants would make it ambiguous.
>
> Sorry for the multiple emails, but I just had another thought. Where is
> the logic in allowing function plugin names that are already used as
> tokens within the parser? Particularly for things like "null", "true",
> etc ?
i think, it's the same logic that allows
$smarty->assign("@$\0\n", $value) even if the $value may be hardly
reachable from the template.
simply not checking is the fastest type of check. :)
> xo boots