Re: weird macro params issue

On 2008.05.23., at 13:51, Denis wrote:

>> Btw how does the multipass deal with
>>
>> <#macro foo=bar bar=foo>

Let's give that macro a name too for easier reference:

<#macro m foo=bar bar=foo>
...

It will resolve both bar in <@m foo="x"/> and foo in <@m bar="x"/>  
invocations correctly. It obviously won't be able to resolve if the  
neither is specified, as in <@x/> and will throw an  
InvalidReferenceException for the first unresolved expression, in this  
case complaining that bar is undefined in foo=bar.

Attila.


-------------------------------------------------------------------------
This SF.net email is sponsored by: Microsoft
Defy all challenges. Microsoft(R) Visual Studio 2008.
http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/