This is the mail archive of the
xsl-list@mulberrytech.com
mailing list .
Fw: Are xsl:key's best going into the future?
- From: "Robert Koberg" <rob at koberg dot com>
- To: <XSL-List at lists dot mulberrytech dot com>
- Date: Fri, 15 Mar 2002 12:23:38 -0800
- Subject: Fw: [xsl] Are xsl:key's best going into the future?
- Reply-to: xsl-list at lists dot mulberrytech dot com
[ I sent this to the list under another address and it bounced ]
> Hi Jeni [just bought your book the other day!],
>
> ----- Original Message -----
> From: "Jeni Tennison" <jeni@jenitennison.com>
> To: "Robert Koberg" <rob@koberg.com>
> Cc: <XSL-List@lists.mulberrytech.com>
> Sent: Friday, March 15, 2002 7:32 AM
> Subject: Re: [xsl] Are xsl:key's best going into the future?
>
>
> > Hi Robert,
> >
> > > In fact, if you want to get the incredible performance gains from
> > > XSLTC, they: [ Xalan's XSLTC team -
> > > http://xml.apache.org/xalan-j/xsltc/xsltc_performance.html ] warn
> > > that you should not use keys.
> > >
> > > Should keys be avoided?
> >
> > Actually, what that document says is that keys shouldn't be used *in
> > patterns*. The example they give is:
> >
> > <xsl:template match="key('key-name', 'some-value')">
> > ...
> > </xsl:template>
>
>
> Thanks, I did take this to mean something different. But, it probably was
> not a good idea for me to include the comment about XSLTC. I was more
> interested in the future of the processors and how they will handle
> currently expensive operations which make xsl:key the obvious choice.
>
> best,
> -Rob
>
XSL-List info and archive: http://www.mulberrytech.com/xsl/xsl-list