Hi,
On Tue, Jan 11, 2011 at 01:45:53PM +0800, wucan wrote:
> On 01/11/2011 12:58 PM, Christian Hergert wrote:
> >Would the TEMP_FAILURE_RETRY() glibc macro be useful here?
> >
> > http://www.gnu.org/s/libc/manual/html_node/Interrupted-Primitives.html
> Well, it should helper, but It's seem there
On 01/11/2011 10:31 PM, Tiago Vignatti wrote:
On Tue, Jan 11, 2011 at 12:00:31PM +0800, ext wucan wrote:
From 5ec4fbccc16d2626e212c2bc1fdec51498b15033 Mon Sep 17 00:00:00 2001
From: wucan
Date: Tue, 11 Jan 2011 11:45:24 +0800
Subject: silence build warning
The read()/write()/pipe() is tagged w
On Tue, Jan 11, 2011 at 12:00:31PM +0800, ext wucan wrote:
> From 5ec4fbccc16d2626e212c2bc1fdec51498b15033 Mon Sep 17 00:00:00 2001
> From: wucan
> Date: Tue, 11 Jan 2011 11:45:24 +0800
> Subject: silence build warning
>
> The read()/write()/pipe() is tagged with __warn_unused_result__
what vers
On 01/11/2011 12:58 PM, Christian Hergert wrote:
Would the TEMP_FAILURE_RETRY() glibc macro be useful here?
http://www.gnu.org/s/libc/manual/html_node/Interrupted-Primitives.html
Well, it should helper, but It's seem there are few codes really use
this macro. I think we all dislike to use it
Would the TEMP_FAILURE_RETRY() glibc macro be useful here?
http://www.gnu.org/s/libc/manual/html_node/Interrupted-Primitives.html
-- Christian
On Mon, Jan 10, 2011 at 8:00 PM, wucan wrote:
> From 5ec4fbccc16d2626e212c2bc1fdec51498b15033 Mon Sep 17 00:00:00 2001
> From: wucan
> Date: Tue, 11
From 5ec4fbccc16d2626e212c2bc1fdec51498b15033 Mon Sep 17 00:00:00 2001
From: wucan
Date: Tue, 11 Jan 2011 11:45:24 +0800
Subject: silence build warning
The read()/write()/pipe() is tagged with __warn_unused_result__
---
clients/dnd.c|7 ---
clients/terminal.c | 12 ++