From: "J.A. Magallon" <jamagallon@able.es>
To: Sam Ravnborg <sam@ravnborg.org>
Cc: "J.A. Magallon" <jamagallon@able.es>,
Jeff Garzik <jgarzik@pobox.com>,
linux-kernel@vger.kernel.org
Subject: Re: Perl in the toolchain
Date: Sat, 1 Feb 2003 00:40:09 +0100 [thread overview]
Message-ID: <20030131234009.GC1541@werewolf.able.es> (raw)
In-Reply-To: <20030131222257.GA11011@mars.ravnborg.org>; from sam@ravnborg.org on Fri, Jan 31, 2003 at 23:22:57 +0100
On 2003.01.31 Sam Ravnborg wrote:
> On Fri, Jan 31, 2003 at 10:38:27PM +0100, 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
> flex and bison is better for this job.
Sure ? KConfig syntax is now context-dependent or the like ?
--
J.A. Magallon <jamagallon@able.es> \ Software is like sex:
werewolf.able.es \ It's better when it's free
Mandrake Linux release 9.1 (Cooker) for i586
Linux 2.4.21-pre4-jam1 (gcc 3.2.1 (Mandrake Linux 9.1 3.2.1-5mdk))
next prev parent reply other threads:[~2003-01-31 23:30 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 [this message]
[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
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=20030131234009.GC1541@werewolf.able.es \
--to=jamagallon@able.es \
--cc=jgarzik@pobox.com \
--cc=linux-kernel@vger.kernel.org \
--cc=sam@ravnborg.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.