This is the mail archive of the
gdb-patches@sourceware.org
mailing list for the GDB project.
Re: [PATCH] Fix 'Undefined command' error message
- From: Eli Zaretskii <eliz at gnu dot org>
- To: Andrew STUBBS <andrew dot stubbs at st dot com>
- Cc: gdb-patches at sources dot redhat dot com
- Date: Wed, 16 Nov 2005 22:00:41 +0200
- Subject: Re: [PATCH] Fix 'Undefined command' error message
- References: <4379EC0A.3060601@st.com> <u1x1h93u5.fsf@gnu.org> <437B2DCC.8020907@st.com>
- Reply-to: Eli Zaretskii <eliz at gnu dot org>
> Date: Wed, 16 Nov 2005 13:02:04 +0000
> From: Andrew STUBBS <andrew.stubbs@st.com>
> Cc: gdb-patches@sources.redhat.com
>
> Eli Zaretskii wrote:
> > Why is there a need for testing *p to be non-zero? AFAIK, isalnum is
> > well defined for a zero argument.
> >
> > What is the reason for additional tests under TUI?
> >
> > Is this for some kind of compatibility with XDB?
>
> I do not know the answer to these questions, although I'm sure I could
> look into it. There are already two instances of this code in this file
> and each is implemented identically to the others.
At least the test for *p non-zero should be removed, I think.
> The reason the code is like this here is because it must replicate the
> tests in lookup_cmd_1 if it is to give the right message. I do not know
> why lookup_cmd_1 is the way it is.
Anyone?