bug-gnulib
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [PATCH] bootstrap: use a more consistent error reporting scheme.


From: Paul Eggert
Subject: Re: [PATCH] bootstrap: use a more consistent error reporting scheme.
Date: Fri, 06 Jul 2012 07:39:46 -0700
User-agent: Mozilla/5.0 (X11; Linux i686; rv:13.0) Gecko/20120615 Thunderbird/13.0.1

On 07/06/2012 07:09 AM, Jim Meyering wrote:
> You're welcome to leave the pipe-to-sed.
> Worrying about an extra process when processing a diagnostic
> is probably a pre-optimization anyhow.

... unless the diagnostic is something like "program failed"
due to lack of enough system resources to fork.

Perhaps the function could use a 'case' to see whether the
format contains '\n' or a newline, and use the pipe-to-sed
only in that case?  It is a bit of a hack, admittedly.



reply via email to

[Prev in Thread] Current Thread [Next in Thread]