Am 11/9/2010 10:35, schrieb Ãvar ArnfjÃrà Bjarmason:
> On Tue, Nov 9, 2010 at 08:33, Johannes Sixt <j.sixt@xxxxxxxxxxxxx> wrote:
>> Am 11/8/2010 23:39, schrieb Ãvar ArnfjÃrà Bjarmason:
>>> eval_gettext () {
>>> gettext "$1" | (export PATH `envsubst --variables "$1"`; envsubst "$1")
>>> }
>>
>> So, for every message printed, you have at least 3 fork()s (usually even
>> more)! I'm not happy about that. You *must* avoid this at least for
>> NO_GETTEXT builds, but if you can reduce them even for no-NO_GETTEXT
>> builds, it would be great.
>
> Why is that a "*must*"?
...
> But maybe you have reason to think otherwise? I haven't noticed any
> noticable slowdowns from doing it this way, but maybe I've been
> looking at the wrong thing.
You didn't do your timings in Windows, did you? Every fork() that you can
avoid is a win.
-- Hannes
--
To unsubscribe from this list: send the line "unsubscribe git" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html