Smarty

[mohrt]

%% was deprecated to keep the template syntax simple, thus keep compiling simple. It may get removed altogether at some point. I'm not adverse to using $_ though, that doesn't add a new var syntax. It also has the variable naming convention of a "private" variable, which makes sense in this case.

I'm still not fond of requiring a new parameter on the section function, internal var references should be automatic and consistant.

[boots]

Okay.

Just to add another idea: maybe we could add a switch/option using a new class member variable to decide if we should automatically create internal private vars for various structures. Perhaps $auto_private_var = true or even $auto_private_var_prefix="_". In the latter case, if null or empty, then use don't auto create vars others prefix the name with the given text. For example, I might choose $auto_private_var_prefix="this_" and in template:

{section name="foo" loop=$bar}
{$this_foo.index}

I guess I would just like to avoid any assumptions on Smarty's part in terms of the namespace.

[messju]

no more config-options please. and especially no config-options that affect template-syntax or semantics.

if you want a shortcut to your section-properties, I'd call it assign:
{section name=foo assign=foo loop=3}{$foo.index}{/section}
(maybe we could make the name optional in that case)

the same would work for {foreach} then.

a case of precedence is {capture}:
{capture name=foo}...{/capture}{$smarty.capture.foo}
was there, and
{capture assign=foo}...{/capture}{$foo}
was added later for convience.
i think this is a little comparable to what you have in mind with section.

[boots]

[mohrt]

[messju]

[quote="mohrt"]

[boots]

Alas. Well, then not using "name" but rather using "alias" or "this" or one of the other suggestions seems appropriate to me. I'm willing to let it go, though....

But riddle me this: why isn't $_smarty_vars pre-populated with the appropriate keys to act as placeholders for the various values it can hold?Something along the lines of:

$_smarty_vars = array('section'=>array(), 'foreach'=>array(), ....);

The reason I ask is because without that little detail I think it makes my alias plugin idea kinda moot since I can't bind to an element that doesn't exist.

[boots]

For me, the worst thing about section is the way that the name property is used in-template. I find the following (standard!) syntax very non-intuitive and not inline with variable handling everywhere else in Smarty:

[tibuda]