mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Sam Ravnborg <sam@ravnborg.org>
To: Jeff Garzik <jgarzik@pobox.com>
Cc: Sam Ravnborg <sam@ravnborg.org>,
	"J.A. Magallon" <jamagallon@able.es>,
	linux-kernel@vger.kernel.org
Subject: Re: Perl in the toolchain
Date: Sat, 1 Feb 2003 13:12:13 +0100	[thread overview]
Message-ID: <20030201121213.GA923@mars.ravnborg.org> (raw)
In-Reply-To: <3E3B0557.3070400@pobox.com>

On Fri, Jan 31, 2003 at 06:23:03PM -0500, Jeff Garzik wrote:
> 
> klibc uses perl for text munging.  i.e. one of Perl's acknowledged 
> strengths.  This is not a case of choosing a favorite script language, 
> but instead a case of choosing "the right tool for the job."

Choosing the right tool for the right job is an argument that matters
in this context.
Two major type of arguments pop's up when selecting diverse tools:
1) "the right tool for the right job"
2) "the most preferred tool"

My main objective is that argument 2) should _not_ be the rationale
behind adding a new tool to the mandatory tool chain.

> Therefore, any rewrite of _this_ _particular_ script in C or shell 
> script would be willfully choosing a sub-optimal implementation language 
> for this task.
The perl scripts used in klibc looks straightforward, expect one that uses
some md5 CPAN module.
Like with C you can in perl pull in a lot of uncommon stuff.

My main objective is to avoid a lot of noise due to one added tool
that may not be required.
Part of the noise will be because people do not understand the
syntax.

> If you take into account the fact that the overwhelming 
> majority of the target audience does indeed have Perl on their system, 
> then that only serves to make it more clear that any such perl-to-C 
> rewrite would not be on any technical nor practical basis at all.

One example could be fixdep:
fixdep could have been done in perl as well. Implementing that one
in c does not count as an "perl-to-C" translation.
To repeat my point.

There is only one good reason to add additional tools to the mandatory
set in the tool-chain. At that reason is that the tool is the right
choice, and not just someones favourite.
If that imply a small C utility then fine.

> Thanks for raising this subject!  I wanted to give your answer some 
> consideration, because it is worth mentioning, and discussing.

Thanks self. I just want to make sure the technically right choice is taken.

	Sam

  parent reply	other threads:[~2003-02-01 12:02 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 [this message]
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
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=20030201121213.GA923@mars.ravnborg.org \
    --to=sam@ravnborg.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®