From: Hans Hagen <pragma@wxs.nl>
To: mailing list for ConTeXt users <ntg-context@ntg.nl>
Subject: Re: lpath question
Date: Fri, 12 Mar 2010 00:00:12 +0100 [thread overview]
Message-ID: <4B9975FC.2040907@wxs.nl> (raw)
In-Reply-To: <5B42A421-EBBE-4A38-8BD7-BE3ACE14F9FC@uva.nl>
On 11-3-2010 22:35, Hans van der Meer wrote:
> In xml processing I have the following element:
> <abc>
> <xyz>contents</xyz>
> <xyz>contents</xyz>
> </abc>
>
> In the code it seems to make no diffence if I write /xyz or xyz without
> the / for the xyz-node.
> {\xmlindex{#1}{/xyz}{1}}
> {\xmlindex{#1}{xyz}{2}}
>
> In the reference manual I find the / used, as for example in
> {\xmlfirst{#1}{/caption}}.
> My question therefore: what exactly causes this behaviour? is it good
> coding practice to always use /xyz in this case?
/ anchors in the #1 node
<a>
<b>
<c>c</c>
</b>
<b>
<c>c</c>
</b>
<c>c</c>
</a>
so, if #1 == a then /c is more restictive than c
also, if you know that you only need the direct child node, it's faster
as there is no need to go deeper
Hans
-----------------------------------------------------------------
Hans Hagen | PRAGMA ADE
Ridderstraat 27 | 8061 GH Hasselt | The Netherlands
tel: 038 477 53 69 | fax: 038 477 53 74 | www.pragma-ade.com
| www.pragma-pod.nl
-----------------------------------------------------------------
___________________________________________________________________________________
If your question is of interest to others as well, please add an entry to the Wiki!
maillist : ntg-context@ntg.nl / http://www.ntg.nl/mailman/listinfo/ntg-context
webpage : http://www.pragma-ade.nl / http://tex.aanhet.net
archive : http://foundry.supelec.fr/projects/contextrev/
wiki : http://contextgarden.net
___________________________________________________________________________________
prev parent reply other threads:[~2010-03-11 23:00 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-03-11 21:35 Hans van der Meer
2010-03-11 23:00 ` Hans Hagen [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=4B9975FC.2040907@wxs.nl \
--to=pragma@wxs.nl \
--cc=ntg-context@ntg.nl \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).