On Thu, Apr 21, 2011 at 11:29 AM, Philip Guenther <guent...@gmail.com> wrote: > On Thu, Apr 21, 2011 at 3:50 AM, David Boyce <david.s.bo...@gmail.com> 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. David _______________________________________________ Bug-make mailing list Bug-make@gnu.org https://lists.gnu.org/mailman/listinfo/bug-make
