This is the mail archive of the
gdb-patches@sourceware.org
mailing list for the GDB project.
Re: [PATCH 4/6] command 'set debug notification'.
- From: Tom Tromey <tromey at redhat dot com>
- To: Joel Brobecker <brobecker at adacore dot com>
- Cc: Yao Qi <yao at codesourcery dot com>, gdb-patches at sourceware dot org
- Date: Wed, 14 Nov 2012 11:12:20 -0700
- Subject: Re: [PATCH 4/6] command 'set debug notification'.
- References: <1348450723-4341-1-git-send-email-yao@codesourcery.com> <1348450723-4341-5-git-send-email-yao@codesourcery.com> <878va55h8a.fsf@fleche.redhat.com> <50A31CE8.6050009@codesourcery.com> <20121114181015.GD5103@adacore.com>
>>>>> "Joel" == Joel Brobecker <brobecker@adacore.com> writes:
Joel> FWIW: I used to prefer boolean, because you can just "set debug blah",
Joel> and it'll enable the debug traces. But some modules have so many
Joel> things to trace about that several levels of verbosity are required.
Joel> In that case, zuinteger becomes necessary.
Yeah, me too.
Joel> Should the needs change over time, I don't think it would be a big deal
Joel> to change the type of the setting from one type (boolean) to another
Joel> (zuinteger), since this is a debug setting. But, technically, that's
Joel> still a non-upward-compatible change - unless we add some extra glue,
Joel> I suppose.
I think we should let ourselves change debug and maint settings without
worrying about compatibility.
But if we're really desperate we can add a "boolean zuinteger" type
where "on" means "1".
Tom