cocoon-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Daniel Fagerstrom <dani...@nada.kth.se>
Subject Re: JXTG macro calling
Date Sat, 26 Feb 2005 21:16:19 GMT
Leszek Gawron wrote:
> Daniel Fagerstrom wrote:
>> Leszek Gawron wrote:
<snip/>
>>> We cannot have two instructions bound to the same jx:param or we will 
>>> again introduce dependencies in Parser.
>>
>> This constraint is, AFAICS, only dependent on that child instructions 
>> has access to their ancestor instructions during compile time. This 
>> means that the diverse param instruction must now which kind of parent 
>> it has to be able to install itself in its parent in the right way.
>>
>> Maybe we could have a "parametrizable" inteface for those instructions 
>> that takes parameters so that the parameter instruction doesn't need 
>> to know more than that the parent is parametrizable.
> 
> Thing is that with the macro parameter definition you have
> <jx:parameter name="something" default="something"/>
> @default being optional
> 
> while with paramter instance you have
> <jx:parameter name="something" value="something"/>
> 
> slightly different semantics.

We could use value instead of default in the first case, XSLT use name 
and select in all cases, OTOH XSLT differ between param and with-param.

Anyway, its no big deal. Just didn't want implementation details limit 
what syntax we chose.

>> It would be even better if we made the refactoring that we discussed 
>> in http://marc.theaimsgroup.com/?t=110651778400003&r=1&w=2 so that 
>> instructions have access to their children during compilation instead 
>> of the other way around.
> 
> It's easier now as we have instructions independent on the Parser. I'll 
> try aiming at that on Monday.
Great!

/Daniel

Mime
View raw message