[Top][All Lists]

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

Re: [bug #33134] spurious error when stdout is already closed

From: David Boyce
Subject: Re: [bug #33134] spurious error when stdout is already closed
Date: Thu, 21 Apr 2011 12:19:29 -0400

On Thu, Apr 21, 2011 at 11:29 AM, Philip Guenther <address@hidden> wrote:
> On Thu, Apr 21, 2011 at 3:50 AM, David Boyce <address@hidden> wrote:
>> All quite true and admirably researched but this is not a
>> standards-lawyering exercise, it's a software-engineering issue.
> Why are you closing stdout instead of redirecting it to /dev/null?

While developing a patch for the .PARALLELSYNC feature being discussed
in another thread (#33138), I tested a number of corner cases which
included stdout being closed. That helped me find some bugs in my work
but I also noticed that even unmodified make had this behavior, so I
submitted a standalone patch to "fix" it.

So - in this context at least - I'm not a user doing a dumb thing, I'm
a developer doing a careful thing. In real life I've never had a valid
reason to close stdout.


reply via email to

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