From: nalaginrut <nalaginrut@gmail.com>
To: Andy Wingo <wingo@pobox.com>
Cc: guile-user@gnu.org
Subject: Re: Is there any xpath2.0 in Guile available?
Date: Thu, 10 Feb 2011 17:10:25 +0800 [thread overview]
Message-ID: <1297329025.2493.9.camel@Renee-desktop> (raw)
In-Reply-To: <m3y65ocm92.fsf@unquote.localdomain>
> On Thu 10 Feb 2011 06:22, nalaginrut <nalaginrut@gmail.com> writes:
>
> > I'm writing a program with xml-based config. I think an xpath2.0
> > implementation would be convenient. Is there any proper module
> > available?
>
> (sxml xpath).
>
> Not well documented though...
>
> Andy
Well~it works now! But I'm glad to see a more detailed document of all
sxml-modules in the future. Thanks!
--
GNU Powered it
GPL Protected it
GOD Blessed it
HFG - NalaGinrut
next prev parent reply other threads:[~2011-02-10 9:10 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <4d52cbe9.c139dc0a.5294.5bdaSMTPIN_ADDED@mx.google.com>
2011-02-09 18:12 ` guile-user Digest, Vol 99, Issue 6 pablo
2011-02-10 5:22 ` Is there any xpath2.0 in Guile available? nalaginrut
2011-02-10 8:44 ` Andy Wingo
2011-02-10 9:10 ` nalaginrut [this message]
2011-02-10 15:14 ` Klaus Schilling
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
List information: https://www.gnu.org/software/guile/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1297329025.2493.9.camel@Renee-desktop \
--to=nalaginrut@gmail.com \
--cc=guile-user@gnu.org \
--cc=wingo@pobox.com \
/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 read-only IMAP folder(s) and NNTP newsgroup(s).