This is the mail archive of the
mailing list for the glibc project.
Re: [PATCH] test-skeleton.c: Use stderr for error messages
- From: Will Newton <will dot newton at linaro dot org>
- To: Siddhesh Poyarekar <siddhesh at redhat dot com>
- Cc: libc-alpha <libc-alpha at sourceware dot org>
- Date: Fri, 11 Apr 2014 14:39:21 +0100
- Subject: Re: [PATCH] test-skeleton.c: Use stderr for error messages
- Authentication-results: sourceware.org; auth=none
- References: <1397210429-28716-1-git-send-email-will dot newton at linaro dot org> <20140411131635 dot GI25518 at spoyarek dot pnq dot redhat dot com>
On 11 April 2014 14:16, Siddhesh Poyarekar <firstname.lastname@example.org> wrote:
> On Fri, Apr 11, 2014 at 11:00:29AM +0100, Will Newton wrote:
>> At the moment a mixture of stderr and stdout is used for error
>> messages. Switch to using stderr for consistency.
>> 2014-04-09 Will Newton <email@example.com>
>> * test-skeleton.c (create_temp_file): Use stderr for
>> outputting error messages. (main): Likewise.
> There was a discussion in the past about sticking to stdout for
> everything for consistency. I can't find the link to it, but it is
> mentioned on the wiki:
So we should really be going the other way and outputting everything to stdout?
At the moment test stdout goes to the test output file but stderr goes
to the console. I'm not sure which is the more useful behaviour but
consistency certainly seems good.
Toolchain Working Group, Linaro