mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Roman Zippel <zippel@linux-m68k.org>
To: "J.A. Magallon" <jamagallon@able.es>
Cc: Jeff Garzik <jgarzik@pobox.com>, <linux-kernel@vger.kernel.org>
Subject: Re: Perl in the toolchain
Date: Fri, 31 Jan 2003 23:51:23 +0100 (CET)	[thread overview]
Message-ID: <Pine.LNX.4.44.0301312343150.9900-100000@serv> (raw)
In-Reply-To: <20030131213827.GA1541@werewolf.able.es>

Hi,

On Fri, 31 Jan 2003, J.A. Magallon wrote:

> instead of
> - do all parsing in perl, that is what perl is for and what is mainly done
>   in kconfig scripts
> - do the config backend in perl, and...

Parsing is only the very first step to generate the dependency tree, which 
is used generate a consistent configuration, so most of the work are 
dependency calculations.
BTW if we use a script language I prefer ruby. :)

bye, Roman


  parent reply	other threads:[~2003-01-31 22:42 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-01-31 18:39 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 [this message]
2003-01-31 23:27       ` Jeff Garzik
2003-01-31 23:40         ` J.A. Magallon
2003-01-31 23:40           ` Jeff Garzik
2003-02-01  0:01           ` Roman Zippel
2003-02-01  0:05             ` J.A. Magallon
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=Pine.LNX.4.44.0301312343150.9900-100000@serv \
    --to=zippel@linux-m68k.org \
    --cc=jamagallon@able.es \
    --cc=jgarzik@pobox.com \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox

all inboxes | Powered by JetHome®