From: Dave Lukes <davel@anvil.com>
To: 9fans <9fans@cse.psu.edu>
Subject: Re: [9fans] OT: small xml parser found!
Date: Thu, 19 Feb 2004 11:04:50 +0000 [thread overview]
Message-ID: <1077188690.30893.104.camel@zevon> (raw)
In-Reply-To: <aa08bd141ebdbe028bf9e6ae3f8f11ea@snellwilcox.com>
Hmmm ...
There's the germ of an idea beginning to grow here ...
Does anyone else need XML parsing? (I said _need_ not _want).
Since I know XML, and want to get my mental fingers
into some plan9 programming, this might _possibly_ be a useful
intellectual exercise.
Cheers,
Dave.
On Thu, 2004-02-19 at 09:59, plan9fans@ntlworld.nospam.com wrote:
> > Why isn't Expat suitable?
>
> Corperate insistance on XML means I may have to read it
> in a small embedded system where "size is everything".
>
> -Steve
next prev parent reply other threads:[~2004-02-19 11:04 UTC|newest]
Thread overview: 32+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-02-19 9:59 plan9fans
2004-02-19 10:13 ` David Tolpin
2004-02-19 11:04 ` Dave Lukes [this message]
2004-02-19 11:41 ` matt
2004-02-19 12:36 ` Dave Lukes
2004-02-19 13:45 ` C H Forsyth
2004-02-20 8:22 ` Martin C.Atkins
-- strict thread matches above, loose matches on Subject: below --
2004-02-19 10:31 plan9fans
2004-02-17 13:50 steve-simon
2004-02-18 18:17 ` Roger Flores
2004-02-18 20:43 ` rog
2004-02-18 20:42 ` David Tolpin
2004-02-19 15:29 ` rog
2004-02-19 15:27 ` Gorka Guardiola Múzquiz
2004-02-19 15:31 ` boyd, rounin
2004-02-19 16:14 ` Rob Pike
2004-02-19 16:16 ` Rob Pike
2004-02-19 16:18 ` David Tolpin
2004-02-19 16:20 ` boyd, rounin
2004-02-19 15:54 ` John Murdie
2004-02-19 16:14 ` C H Forsyth
2004-02-19 16:24 ` John Murdie
2004-02-19 16:17 ` David Tolpin
2004-02-20 2:36 ` boyd, rounin
2004-02-19 17:15 ` rog
2004-02-19 17:20 ` David Tolpin
2004-02-19 17:31 ` rog
2004-02-19 17:30 ` David Tolpin
2004-02-19 17:45 ` rog
2004-02-19 17:39 ` C H Forsyth
2004-02-19 15:27 ` David Tolpin
2004-02-19 10:28 ` Roger Flores
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=1077188690.30893.104.camel@zevon \
--to=davel@anvil.com \
--cc=9fans@cse.psu.edu \
/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).