Date: Fri, 3 Mar 2006 10:08:58 +0200 (EET) From: Dmitry Pryanishnikov <dmitry@atlantis.dp.ua> To: "Greg 'groggy' Lehey" <grog@FreeBSD.org> Cc: freebsd-current@FreeBSD.org, Robert Watson <rwatson@FreeBSD.org>, cperciva@FreeBSD.org, "M. Warner Losh" <imp@bsdimp.com> Subject: Re: style(9) question Message-ID: <20060303100241.E42653@atlantis.atlantis.dp.ua> In-Reply-To: <20060303004506.GA13218@wantadilla.lemis.com> References: <4407226D.3050901@freebsd.org> <20060302171112.A77029@fledge.watson.org> <20060302105229.P83093@atlantis.atlantis.dp.ua> <20060302163633.H77029@fledge.watson.org> <4407226D.3050901@freebsd.org> <20060302.100922.130234735.imp@bsdimp.com> <20060302105229.P83093@atlantis.atlantis.dp.ua> <20060302.100608.80501136.imp@bsdimp.com> <20060302105229.P83093@atlantis.atlantis.dp.ua> <200002110637.RAA79715@freebie.lemis.com> <20060303004506.GA13218@wantadilla.lemis.com>
next in thread | previous in thread | raw e-mail | index | archive | help
Hello! On Fri, 3 Mar 2006, Greg 'groggy' Lehey wrote: >> Before 'void' existed, many people recommended () so that you could >> make 'return' a macro for extra debugging. With void functions that >> have naked returns make this impossible these days... > > This is actually a useful property. Pity it's gone. It's gone only for void functions. Anyway programmer usually wants to debug code on function-by-function basis, and one can still #define return macros for one (non-void) function and #undef it after this function. Sincerely, Dmitry -- Atlantis ISP, System Administrator e-mail: dmitry@atlantis.dp.ua nic-hdl: LYNX-RIPE
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20060303100241.E42653>