Re: [xsl] Yet Another Flat File to Hierarchy question..

["Kurt Cagle" <cagle@xxxxxxxxx>]

In the Microsoft parser, xsl:key operations are performed before a context
is instantiated (for performance reasons, according to the implementer).
That's one of the big reasons I avoid use of xsl:key, at least in the MSXML
implementations.

----- Original Message -----
From: "Bill Cohagan" <bill.cohagan@xxxxxxxxxxxxx>
To: <xsl-list@xxxxxxxxxxxxxxxxxxxxxx>
Sent: Friday, June 14, 2002 11:02 AM
Subject: RE: [xsl] Yet Another Flat File to Hierarchy question..


> I think the problem you're seeing is related to the problem I described in
> my recent post regarding xsl:key semantics and MSXML. First, a good test
> would be to try your case using Saxon 6.5.2 which appears to "do the right
> thing" with the call to current(), at least for my testcase. I believe
> earlier versions do not. MSXML (any version) does NOT do the right thing
as
> far as I can tell. (Xalan may also be a way to test your case. I
understand
> that it works properly too.)
>
> Regards,
>  Bill
>
>  -----Original Message-----
> From: McNally, David [mailto:David.McNally@xxxxxxxxxx]
> Sent: Friday, June 14, 2002 12:56 PM
> To: 'xsl-list@xxxxxxxxxxxxxxxxxxxxxx'
> Subject: RE: [xsl] Yet Another Flat File to Hierarchy question..
>
> For some reason I can't get current() to work in key definitions - or at
> least that seems to be what the problem is.  Using the suggested key
below,
> I tried this xslt:
>
> <snip>
>
>  XSL-List info and archive:  http://www.mulberrytech.com/xsl/xsl-list
>
>



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