This is the mail archive of the
xsl-list@mulberrytech.com
mailing list .
Re: quick table layout problem
- From: David Carlisle <davidc at nag dot co dot uk>
- To: xsl-list at lists dot mulberrytech dot com
- Date: Mon, 7 Jan 2002 15:47:51 GMT
- Subject: Re: [xsl] quick table layout problem
- References: <000c01c1978e$f7360f70$8ac809c0@ajw>
- Reply-to: xsl-list at lists dot mulberrytech dot com
> what xpath expression will match the first <e>, without using //
match="e"
If you mean match, if you mean select then something like
(/a/b[3]/c/d/e)[1]
> As a point of interest, what kind of performance hit does using // give?
If used with [1] as in (//e)[1] then probably not much, in either case
the system will stop once it comes to the first e, but if you compare
/a/b/c/d/e
and //e
then the first will only need to search teh document to a fixed depth
to look for e's whereas //e will always have to search the entire
document. You may know that a ,z> element never has any e descendents,
but the system doesn't and so will have to look everywhere 9including
inside e elements) to check for e children On big documents that can be
quite a hit.
In your table example you know I think that entry are always two levels
down from table so table/*/*/entry is likely to be a lot nicer to the
system than table//entry.
David
_____________________________________________________________________
This message has been checked for all known viruses by Star Internet
delivered through the MessageLabs Virus Scanning Service. For further
information visit http://www.star.net.uk/stats.asp or alternatively call
Star Internet for details on the Virus Scanning Service.
XSL-List info and archive: http://www.mulberrytech.com/xsl/xsl-list