git/list[1] front-page[2] threads[3] people[4] search[5] about
 

Re: [PATCH] Eliminate Scalar::Util usage from private-Error.pm

From
LTLuben Tuikov <ltuikov@yahoo.com>
Date
Jul 26, 2006, 17:59 UTC
Message-ID
<20060726175931.37750.qmail@web31810.mail.mud.yahoo.com>
In-Reply-To
<Pine.LNX.4.63.0607261702500.29667@wbgn013.biozentrum.uni-wuerzburg.de>
--- Johannes Schindelin <Johannes.Schindelin@gmx.de> wrote:
Show 14 quoted lines
> Hi,
> 
> [please do not remove me from the Cc: when replying to my mail]
> 
> On Wed, 26 Jul 2006, Jakub Narebski wrote:
> 
> > Johannes Schindelin wrote:
> > 
> > > Seriously, I still believe that proof-of-concepts in Bash or Perl or even 
> > > Python are fine. But they are not for real work, so one of my long-term 
> > > goals for git is to get rid of them.
> > 
> > I don't think that we would want to rewrite gitweb in C, for example.
> > And Perl for porcelanish commands is all right, IMVVHO.

I agree with Jakub. Both on the deployment side and on the maintenance and upkeeping side. Small and fast engine in C and porcelain in whatever makes sense: Perl, Python, Bash, or even C, etc.

> This is true as long as you do not have problems with Perl. As soon as you 
> start having too many problems with Perl, you want to get rid of it as 
> soon as possible.

The normal thing to do is to post an email to the mailing list describing the problems you see with Perl, and describing your solution to them, possibly accompanied with a patch. But to just post a "convert-to-C" patch is hardly constructive (to the actual problem you had).

> Think missing modules. Think ActiveState. Think corporate environment. 
> Think other platforms. Think having to mix compilers. Or to support 
> another one, because you cannot mix. Etc. etc.

Yep, exactly _those_ reasons you outlined, tell me that some things are _better_ off staying in Perl/Python/etc.

    Luben
Previous: Johannes SchindelinNext: Randal L. Schwartz
Message 15 of 21 in “cvsserver: avoid warning about active db handles”
  1. cvsserver: avoid warning about active db handlesJohannes Schindelin, Jul 25, 2006
  2. Martin Langhoff (CatalystIT)Jul 25, 2006
  3. Johannes SchindelinJul 25, 2006
  4. Petr BaudisJul 25, 2006
  5. Git.xs problem, was Re: [PATCH] cvsserver: avoid warning about active db handlesJohannes Schindelin, Jul 25, 2006
  6. Eliminate Scalar::Util usage from private-Error.pmPetr Baudis, Jul 26, 2006
  7. Johannes SchindelinJul 26, 2006
  8. Johannes SchindelinJul 26, 2006
  9. Petr BaudisJul 26, 2006
  10. Johannes SchindelinJul 26, 2006
  11. Petr BaudisJul 26, 2006
  12. Johannes SchindelinJul 26, 2006
  13. Jakub NarebskiJul 26, 2006
  14. Johannes SchindelinJul 26, 2006
  15. Luben TuikovJul 26, 2006
  16. Randal L. SchwartzJul 27, 2006
  17. Johannes SchindelinJul 27, 2006
  18. Randal L. SchwartzJul 27, 2006
  19. Johannes SchindelinJul 27, 2006
  20. Petr BaudisJul 26, 2006
  21. Petr BaudisJul 26, 2006

Read the whole thread, see it on lore, or plain text.

$ cat FOOTERMessages come from the public archive at lore.kernel.org/git, fetched every hour. The front page is chosen and written each morning by an AI editor and can be wrong; the threads themselves are the record. About and API. For agents: an MCP server at https://gitlist.dev/mcp, and any thread, story or person page as Markdown by adding .md to its URL (or sending Accept: text/markdown). Details in /llms.txt.