Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1761914AbXEVNxS (ORCPT ); Tue, 22 May 2007 09:53:18 -0400 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S1756661AbXEVNxI (ORCPT ); Tue, 22 May 2007 09:53:08 -0400 Received: from seahorse.shentel.net ([204.111.1.244]:47996 "EHLO seahorse.shentel.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1756564AbXEVNxH (ORCPT ); Tue, 22 May 2007 09:53:07 -0400 Date: Tue, 22 May 2007 09:53:03 -0400 (EDT) From: "John Anthony Kazos Jr." To: "Robert P. J. Day" cc: Linux Kernel Mailing List Subject: Re: any value to "NORET_TYPE" macro? In-Reply-To: Message-ID: References: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=us-ascii Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 1001 Lines: 24 > given that: > > $ grep -r "define.*NORET_TYPE" * > include/linux/ext4_fs.h:# define NORET_TYPE /**/ > include/linux/linkage.h:#define NORET_TYPE /**/ > include/linux/ext3_fs.h:# define NORET_TYPE /**/ > $ > > is there any obvious value to the 30 or so uses of that macro > sprinkled throughout the tree? Since it evaluates to absolutely empty code during pre-processing, there is no obvious value. The question is whether there is some odd hackish non-obvious value, I'd expect. (I'd also expect that to be another "no".) If something that evaluates to nothingness ("There was nothing left...not even a hole!") actually does anything, then somebody in the standards-compilers-users pipeline needs to be violently beaten for stupidity. - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/