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 01:04:54 +0200 [thread overview]
Message-ID: <200506300104.54795.mbuesch@freenet.de> (raw)
In-Reply-To: <635171.636ad3ed642208e93e44c79901f90691e930c5afe6b95fe3e707420e71193c0022f01e95.IBX@taniwha.stupidest.org>
[-- Attachment #1: Type: text/plain, Size: 972 bytes --]
Quoting Chris Wedgwood <cw@f00f.org>:
> On Thu, Jun 30, 2005 at 12:25:03AM +0200, Michael Buesch wrote:
>
> > Search the archives.
> > There was a thread about this some time ago.
>
> that doesn't make it a good idea
I did not say that. Indeed I say it's a bad idea.
And that was also the conclusion in the other thread I talked about.
I only gave this example here, because people often think
xml parsers are big with many lines of code. This one is only
about 500 lines. But still, please don't put such unneccessary
bloat into the kernel. ;)
> > 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
>
> all this tells me is that some desktop application programmer wants to
> put XML into the kernel
not me. ;)
--
Greetings, Michael
[-- Attachment #2: Type: application/pgp-signature, Size: 189 bytes --]
next prev parent reply other threads:[~2005-06-29 23:07 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
2005-06-29 22:52 ` Chris Wedgwood
2005-06-29 23:04 ` Michael Buesch [this message]
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=200506300104.54795.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