This is the mail archive of the gdb-patches@sourceware.org mailing list for the GDB project.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]
Other format: [Raw text]

Re: [RFA] candidates for ambiguous command in upper case


On 01/16/2017 07:58 PM, Pedro Alves wrote:
On 01/16/2017 04:32 PM, Jerome Guitton wrote:
Pedro Alves (palves@redhat.com):

Dunno, if it doesn't make sense, and nobody uses it, then it's one
less thing to maintain and test.

Hard to figure out if someone uses it, I guess. This originally got
reported by one of our users as a minor inconsistancy, who also said
that he would be OK if gdb commands were case sensitive.

The patch that I'm suggesting is fairly simple, but my feeling is that
it would be just as easy to remove the feature.

I've tested the opposite: making the match case sensitive is a matter
of removing 4 characters in cli-decode.c. Not much consequences in the
testsuite. "handle sigq" still completes to "handle SIGQUIT".

So, what do we want to do?
1. Remove the feature?
2. Improve its consistency?
3. Keep things as is?


I vote #1.

I don't see a problem with #1 as long as we keep it consistent throughout from now on.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]