Re: gnulib-tool --import slowness

[Simon Josefsson]

Bruno Haible <address@hidden> writes:

> But "top" doesn't show these sed processes; it shows the gnulib-tool
> script itself eating the time. I guess the problem is the double loop
> over the new file and the old files. This is quadratic in the number of
> files. I'll change this to use "join" and "sort" instead of a double loop.

Thanks.

>> Can't we use
>>
>> perl -pi -e 's/foo/bar' *.c
>>
>> or something else instead?
>
> Using perl instead of sed to gain speed? Nice joke :-)

Heh.  I was mostly referring to the *.c part, instead of invoking sed
for every file specifically.

> Besides that, I never use perl, because
>   - perl's syntax is so complex that it's nearly impossible to understand
>     a program just by reading its source code,
>   - the perl developers don't care much about backward compatibility, as
>     you can see from the Unicode changes between perl 5.4 - 5.6 - 5.8;
>     therefore you must be prepared to rewrite your scripts every two or
>     three years.
> Stick to /bin/sh instead.

Right.