Re: [SMARTY-DEV] Re: literal and javascript
| From: | Mark Rogers | Date: | Thu, 18 Mar 2004 17:45:28 +0000 |
| Subject: | Re: [SMARTY-DEV] Re: literal and javascript | ||
| References: | 1 2 3 4 5 6 | Groups: | php.smarty.dev |
| Request: | Send a blank email to php-smarty-dev+get-2224@lists.php.net to get a copy of this message | ||
Pete M writes:
> Does IT - not my side ????? this is all I want !!!!
>
> > For one, I'd expect this to work as it does right now (taken from the
> Smarty
> > docs):
> > {literal}
> > SYNTAX EXAMPLES:
> > {func var="test
$foo.bar test"} <-- sees
> > $foo.bar
> > {/literal}
We're probably talking at cross purposes.
The text above will show exactly as written, the backticks are not
interpretted. This is as it should be, so that a syntax example, such as
that above, can be run through Smarty protected by {literal} without being
touched. Otherwise we couldn't (easily) use Smarty to document Smarty...
This is not what you want; you are wishing to change {literal}'s behaviour
on the basis that backticks would be more usefully interpretted than not.
What I posted was a (badly explained) example of why this would be a bad
thing.
FYI: I have a working {script}{/script} block handler now as described
elsewhere; that works quite well for stuff like this.
--
Mark Rogers,
More Solutions Ltd :: Tel: 0845 45 89 555