From: "Eric S. Raymond" <esr@thyrsus.com>
To: Jean-Luc Leger <reiga@dspnet.fr.eu.org>
Cc: Linux Kernel List <linux-kernel@vger.kernel.org>
Subject: Re: CML2-2.3.0 is available
Date: Fri, 15 Feb 2002 11:35:52 -0500 [thread overview]
Message-ID: <20020215113552.A7351@thyrsus.com> (raw)
In-Reply-To: <20020214193329.A23463@thyrsus.com> <20020215042631.A23535@zalem.nrockv01.md.comcast.net> <20020215090624.B3047@thyrsus.com> <20020215173504.B85139@dspnet.fr.eu.org>
In-Reply-To: <20020215173504.B85139@dspnet.fr.eu.org>; from reiga@dspnet.fr.eu.org on Fri, Feb 15, 2002 at 05:35:04PM +0100
Jean-Luc Leger <reiga@dspnet.fr.eu.org>:
> On Fri, Feb 15, 2002 at 09:06:24AM -0500, Eric S. Raymond wrote:
> > Symbol type is inferred from use in a menu.
>
> what about those "legend" symbols that were in menus list but with
> no menu declaration ?
>
> ex:
> menu usb # USB? support
> USB_DEBUG
> usb_options_legend
> USB_DEVICEFS USB_BANDWIDTH USB_LONG_TIMEOUT
> usb_controllers_legend
> h:USB_UHCI? h:USB_UHCI_ALT? h:USB_OHCI?
> ...
>
> I see no difference in use for usb_options_legend and USB_DEBUG.
Good catch! Messages had been temporarily disabled, but I finished
adding a message declaration suffix (!) just before your mail came in.
In 2.3.1 your example will look like this.
menu usb # USB? support
USB_DEBUG
usb_options_legend!
USB_DEVICEFS USB_BANDWIDTH USB_LONG_TIMEOUT
usb_controllers_legend!
h:USB_UHCI? h:USB_UHCI_ALT? h:USB_OHCI?
...
The reason for this change in design is to make it easier to automatically
generate per-directory distributed symbols files. But the good thing about
it is that it simplifies the language -- I was able to remove three constructs
and only have to add back one.
--
<a href="http://www.tuxedo.org/~esr/">Eric S. Raymond</a>
prev parent reply other threads:[~2002-02-15 17:01 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-02-15 0:33 CML2-2.3.0 is available Eric S. Raymond
2002-02-15 6:51 ` Robert Schwebel
2002-02-15 9:18 ` Thomas Capricelli
2002-02-15 9:26 ` Olivier Galibert
2002-02-15 14:06 ` Eric S. Raymond
2002-02-15 16:35 ` Jean-Luc Leger
2002-02-15 16:35 ` Eric S. Raymond [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20020215113552.A7351@thyrsus.com \
--to=esr@thyrsus.com \
--cc=linux-kernel@vger.kernel.org \
--cc=reiga@dspnet.fr.eu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox