RE: Re: Re: Should variable resolution be done at compile-time or run-ti

xsl-list

RE: Re: Re: Should variable resolution be done at compile-time or run-time?

2003-10-19 13:24:38

So, why do you think that:

 the reference to the undeclared
(or out-of-scope) variable does actually appear to be evaluated.


I stand corrected, I didn't read the posting carefully enough.

Michael Kay


 XSL-List info and archive:  http://www.mulberrytech.com/xsl/xsl-list

<Prev in Thread]	Current Thread	[Next in Thread>
Should variable resolution be done at compile-time or run-time?, Eric Promislow Re: Should variable resolution be done at compile-time or run-time?, G. Ken Holman RE: Should variable resolution be done at compile-time or run-time?, Lars Huttar Re: Should variable resolution be done at compile-time or run-time?, Dimitre Novatchev RE: Re: Should variable resolution be done at compile-time or run-time?, Michael Kay Re: Re: Should variable resolution be done at compile-time or run-time?, Dimitre Novatchev RE: Re: Re: Should variable resolution be done at compile-time or run-time?, Michael Kay <=

Previous by Date:	XSL-FO Property Resolution / Expressions, Stefan Hermann
Next by Date:	sort problem, Edward Maesen
Previous by Thread:	Re: Re: Should variable resolution be done at compile-time or run-time?, Dimitre Novatchev
Next by Thread:	to generate <table columns> with widths using a "lookup-table/list/array in the xsl" for a customizable XSL-FO & XSL-HTML, SANWAL, ABHISHEK (HP-Houston)
Indexes:	[Date] [Thread] [Top] [All Lists]