[XSL-LIST Mailing List Archive Home] [By Thread] [By Date] [Recent Entries] [Reply To This Message] Re: xsl:key in a function?
On 2012-03-05 23:32, Andrew Welch wrote:
On 5 March 2012 21:56, ihe onwuka<ihe.onwuka@xxxxxxxxxxxxxx> wrote:On Mon, Mar 5, 2012 at 8:15 PM, Andrew Welch<andrew.j.welch@xxxxxxxxx> wrote:Well I know the solution - keys, read the file once and stick it in a variable, however this is not an option because they don't want to let me tweak the generated code. I wasnt in yet, but Im out, too. Wrong life cannot be lived rightly. Next year, I promise, youll see a brand new Adorno quotation, because apparently I used this one before: http://markmail.org/search/?q=wrong%20life%20rightly%20gerrit#query:wrong%20life%20rightly%20gerrit+page:1+mid:vmyo2mz7kzxmat3f+state:results Its not that Im against generating code. Generating XSLT code (particularly: generating matching patterns) can give you lots of flexibility without the need to sacrifice performance. But generated for-each instructions is a different game, its plain wrong life in most cases, wronger than poor XQuerys typeswitch statement. Because we can do better. One of the worst pieces of XSLT code that Ive ever seen was some xsl:for-each ejaculate that came straight off of an Altova StyleVision file. Maybe it was maintainable with StyleVision, which I dont use. But fixing the generated XSLT code seemed to be so much more effort than re-creating more reasonable transformations from scratch, and thats what we did. Redesigning their generator code may prove to be worth the while. Gerrit
|
PURCHASE STYLUS STUDIO ONLINE TODAY!Purchasing Stylus Studio from our online shop is Easy, Secure and Value Priced! Download The World's Best XML IDE!Accelerate XML development with our award-winning XML IDE - Download a free trial today! Subscribe in XML format
|