This is the mail archive of the xsl-list@mulberrytech.com mailing list .


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]
Other format: [Raw text]

RE: DOM and XML parser


Hi Jeny!
I see, so that means something like match="book[(%1=@price)]". being so
that also means that we could do something like
match="book[%@price]|magazine[@price=%1]"??

that could be handy :)

-----Original Message-----
From: owner-xsl-list@lists.mulberrytech.com
[mailto:owner-xsl-list@lists.mulberrytech.com] On Behalf Of Jeni
Tennison
Sent: Monday, August 19, 2002 3:57 PM
To: Américo Albuquerque
Cc: xsl-list@lists.mulberrytech.com
Subject: Re: [xsl] DOM and XML parser


Hi Américo,

> yes, it is an interesting idea. but that whouldn't be the same as
> setting the variable after the match??
> like:
> <xsl:template match="book[@price]">
>  <xsl:variable name="v" select="@price"/>
>  ...

The same in effect, yes, but the point in fxgrep is that with:

<xsl:template match="book[%@price]">
  ...
</xsl:template>

the price attribute could be bound to the variable *during* the matching
rather than after finding the node. This saves you from having to scan
the node and its relationships with other nodes more than once, which is
particularly useful as you get to use more complex match patterns.

Anyway, I'm not particularly advocating the idea -- I wouldn't want to
see XSLT complicated in this way (after all, it's getting complicated
enough by XPath 2.0 without anything like this!) -- just thought it was
an interesting approach.

Cheers,

Jeni

---
Jeni Tennison
http://www.jenitennison.com/


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



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


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]