Re: [PATCH] Add git-annotate - a tool for annotating files with the revision and person that created each line in the file.

From: Andreas Ericsson <ae@op5.se>
Date: Feb 9, 2006, 12:47 UTC
Message-ID: <43EB39C4.3020309@op5.se>
In-Reply-To: <cda58cb80602090404o4e753839g@mail.gmail.com>

Franck Bui-Huu wrote:

Show 15 quoted lines

> 2006/2/9, Junio C Hamano <junkio@cox.net>:
> 
>>Andreas Ericsson <ae@op5.se> writes:
>>
>>
>>>So long as we never involve ruby, java or DCL, I'm a happy fellow.
>>
>>Wholeheartedly seconded ;-).
>>
> 
> 
> I agree to but my point was more why not only using python scripts ?
> Why sometimes some scripts is written in perl whereas python could be
> used and vice-versa ?
>

Perl is better suited for some tasks, Python for others. Mostly it's because the contributor (one out of 137 to date) thought the language appropriate for the tool he/she set out to write and felt comfortable with it.

I personally abhor the syntax of Perl and the block indentation of Python but I happily embrace both if the alternative is to rewrite all the script tools in C.

That said, some tools have been rewritten in the past (mostly scripts have been replaced by C code versions), but I don't think Junio will accept replacement tools just because they're in one particular language. If anything, it would be to replace the two python scripts with Perl versions, since more tools are implemented in Perl than in Python (so we could drop one dependency), Perl exists on more platforms (so git becomes more portable), and Perl is used inline in four of the shell-scripts (which means we can't get rid of the Perl dependency without major hackery anyway).

-- 
Andreas Ericsson                   andreas.ericsson@op5.se
OP5 AB                             www.op5.se
Tel: +46 8-230225                  Fax: +46 8-230231