From: Aron Griffis Subject: Re: [PATCH] Check some returns of common functions Date: Wed, 26 Apr 2006 15:02:35 -0400 Message-ID: <20060426190235.GE8029@olive.flatmonk> References: <1146017884.3007.13.camel@aglarond.local> <20060426082913.GA19433@leeni.uk.xensource.com> <5875df1124b997794c1db7a8332b9be3@cl.cam.ac.uk> Mime-Version: 1.0 Content-Type: text/plain; charset=utf-8 Return-path: Content-Disposition: inline In-Reply-To: <5875df1124b997794c1db7a8332b9be3@cl.cam.ac.uk> List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: xen-devel-bounces@lists.xensource.com Errors-To: xen-devel-bounces@lists.xensource.com To: xen-devel@lists.xensource.com List-Id: xen-devel@lists.xenproject.org Keir Fraser wrote: [Wed Apr 26 2006, 04:52:16AM EDT] > The following might be clearer than doing the workaround in-place > though: > > #define ignore_retval(x) do { long __r; __r = (long)(x); } while (0) How is a custom wrapper clearer than (void), which is generally recognized as intentionally ignoring the return value? Aron