Re: tokens as input to modifiers
boots <[email protected]>
| Newsgroups | gmane.comp.php.smarty.devel |
|---|---|
| Message-ID | <[email protected]> |
> --- messju mohr <[email protected]> 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 ? xo boots -- Smarty Development Mailing List (http://smarty.php.net/) To unsubscribe, visit: http://www.php.net/unsub.php