From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1764864AbXGUTRv (ORCPT ); Sat, 21 Jul 2007 15:17:51 -0400 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S1758962AbXGUTRp (ORCPT ); Sat, 21 Jul 2007 15:17:45 -0400 Received: from nic.NetDirect.CA ([216.16.235.2]:49867 "EHLO rubicon.netdirect.ca" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1754711AbXGUTRo (ORCPT ); Sat, 21 Jul 2007 15:17:44 -0400 X-Originating-Ip: 72.143.66.27 Date: Sat, 21 Jul 2007 15:15:55 -0400 (EDT) From: "Robert P. J. Day" X-X-Sender: rpjday@localhost.localdomain To: Jan Engelhardt cc: Linux Kernel Mailing List Subject: Re: [PATCH] Use menuconfig objects - Fusion In-Reply-To: Message-ID: References: <200705102317.l4ANHrUC001117@shell0.pdx.osdl.net> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-Net-Direct-Inc-MailScanner-Information: Please contact the ISP for more information X-Net-Direct-Inc-MailScanner: Found to be clean X-Net-Direct-Inc-MailScanner-SpamCheck: not spam, SpamAssassin (not cached, score=-36.8, required 5, autolearn=not spam, ALL_TRUSTED -1.80, BAYES_00 -15.00, INIT_RECVD_OUR_AUTH -20.00) X-Net-Direct-Inc-MailScanner-From: rpjday@mindspring.com Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org On Sat, 21 Jul 2007, Jan Engelhardt wrote: > > On Jul 21 2007 15:05, Robert P. J. Day wrote: > >> +menuconfig FUSION > >... > >> +if FUSION > >> > >> config FUSION_SPI > >... > >> +endif # FUSION > > > > i just *know* i'm going to regret asking this, but is there a > >compelling reason why the internal contents of a "menuconfig FUBAR" > >needs to still be surrounded by a "if FUBAR" condition? > > Note that if/endif actually translates to a "depends on" for every > contained object. I prefer the reduced clutter [if/endif] over > having explicit depends on on every object, since it is redundant. oh, i absolutely agree with you there. > >wouldn't it be philosophically cleaner if the internals of a > >menuconfig structure *automatically* depended on selection of the > >menuconfig and the "if" part was implicit? > > "menuconfig" is not a start marker like "menu" was. Hence it has no > "stop" marker either. We would need a new object type for that. http://www.linuxrocket.net/index.cgi?a=MailArchiver&ma=ShowMail&Id=525787 rday -- ======================================================================== Robert P. J. Day Linux Consulting, Training and Annoying Kernel Pedantry Waterloo, Ontario, CANADA http://fsdev.net/wiki/index.php?title=Main_Page ========================================================================