From: Michael Buesch <mbuesch@freenet.de>
To: Chris Wedgwood <cw@f00f.org>
Cc: linux-kernel@vger.kernel.org, Ville Sundell <ville.sundell@gmail.com>
Subject: Re: Build-in XML support?
Date: Thu, 30 Jun 2005 00:25:03 +0200 [thread overview]
Message-ID: <200506300025.03544.mbuesch@freenet.de> (raw)
In-Reply-To: <715093.8e23073dd5b3768051865c10fd31f542c39a3531079809488fc0f500cacb255a2afd49c2.ANY@taniwha.stupidest.org>
[-- Attachment #1: Type: text/plain, Size: 1082 bytes --]
Quoting Chris Wedgwood <cw@f00f.org>:
> On Wed, Jun 29, 2005 at 01:51:06PM +0300, Ville Sundell wrote:
>
> > I know, this maybe is F.A.Q, but I ask it anyway (because I have not found it
> > in kernel mail-list, so don't shot me!):
>
> <bang>
>
> > How about build-in XML-support to kernel?
>
> What problem is this solving?
>
> > Good or bad?
>
> Utterly pointless
>
> > It would be wery useful for config-files?
>
> The kernel doesn't have config files, just knobs in proc/sysfs.
>
> > (...and I have a draft for small XML-parser in C-language;) )
Search the archives.
There was a thread about this some time ago.
Tim Hockin talked about his XML parser there. I'm currently
using it (in a modified form) in some of my programs:
xmlparser.h:
http://websvn.kde.org/branches/pwmanager/1.2/pwmanager/pwmanager_dump/xmlparser.h?rev=416745&view=markup
xmlparser.c:
http://websvn.kde.org/branches/pwmanager/1.2/pwmanager/pwmanager_dump/xmlparser.c?rev=417577&view=markup
Sorry for the half-offtopic posting. :D
--
Greetings, Michael
[-- Attachment #2: Type: application/pgp-signature, Size: 189 bytes --]
next prev parent reply other threads:[~2005-06-29 22:26 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-06-29 10:51 Build-in XML support? Ville Sundell
2005-06-29 22:07 ` Chris Wedgwood
2005-06-29 22:25 ` Michael Buesch [this message]
2005-06-29 22:52 ` Chris Wedgwood
2005-06-29 23:04 ` Michael Buesch
2005-06-29 23:07 ` Chris Wedgwood
2005-06-30 9:09 ` Ville Sundell
2005-06-30 9:17 ` Matti Aarnio
2005-06-30 14:06 ` Ken Moffat
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=200506300025.03544.mbuesch@freenet.de \
--to=mbuesch@freenet.de \
--cc=cw@f00f.org \
--cc=linux-kernel@vger.kernel.org \
--cc=ville.sundell@gmail.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