From: Jeff Garzik <jgarzik@pobox.com>
To: "J.A. Magallon" <jamagallon@able.es>
Cc: linux-kernel@vger.kernel.org
Subject: Re: Perl in the toolchain
Date: Fri, 31 Jan 2003 18:40:40 -0500 [thread overview]
Message-ID: <3E3B0978.7080900@pobox.com> (raw)
In-Reply-To: <20030131234021.GE1541@werewolf.able.es>
J.A. Magallon wrote:
> As someone said, parsing and string processing is one of the jobs in kernel
> config. Kernel gurus decided to rewrite the thing in C to avoid the lacks
> in the current bash-ish kconfig, because writing logic for dependencies,
> checks and so on is a pain...so let's rewrite the logic handling, _and_ the
> string processing, btw.
> The easies way (from my point of view): write Perl::KConfig in C to do the logic
> hard work and build the big thing in perl. That will be putting a perl
> interface on top of klibc ?
_Any_ rewrite is pure pedantry and useless work.
next prev parent reply other threads:[~2003-01-31 23:33 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-01-31 18:39 Perl in the toolchain Pete Zaitcev
2003-01-31 19:41 ` Kai Germaschewski
2003-01-31 19:48 ` Jeff Garzik
2003-01-31 19:55 ` Mr. James W. Laferriere
2003-01-31 20:41 ` Sam Ravnborg
2003-01-31 22:50 ` Ben Greear
2003-01-31 21:38 ` J.A. Magallon
2003-01-31 22:22 ` Sam Ravnborg
2003-01-31 23:23 ` Jeff Garzik
2003-02-01 0:29 ` H. Peter Anvin
2003-02-01 12:12 ` Sam Ravnborg
2003-01-31 23:40 ` J.A. Magallon
[not found] ` <mailman.1044055681.1939.linux-kernel2news@redhat.com>
2003-02-01 1:06 ` Pete Zaitcev
2003-02-01 6:02 ` Ryan Anderson
2003-01-31 22:51 ` Roman Zippel
2003-01-31 23:27 ` Jeff Garzik
2003-01-31 23:40 ` J.A. Magallon
2003-01-31 23:40 ` Jeff Garzik [this message]
2003-02-01 0:01 ` Roman Zippel
2003-02-01 0:05 ` J.A. Magallon
-- strict thread matches above, loose matches on Subject: below --
2003-01-31 20:13 Ed Vance
2003-02-01 3:28 ` Scott Robert Ladd
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=3E3B0978.7080900@pobox.com \
--to=jgarzik@pobox.com \
--cc=jamagallon@able.es \
--cc=linux-kernel@vger.kernel.org \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.