This is the mail archive of the
gdb-patches@sourceware.org
mailing list for the GDB project.
Re: [PATCH 4/4] compile: New 'compile print'
- From: Eli Zaretskii <eliz at gnu dot org>
- To: Jan Kratochvil <jan dot kratochvil at redhat dot com>
- Cc: gdb-patches at sourceware dot org, pmuldoon at redhat dot com
- Date: Fri, 27 Mar 2015 10:41:15 +0300
- Subject: Re: [PATCH 4/4] compile: New 'compile print'
- Authentication-results: sourceware.org; auth=none
- References: <20150326205727 dot 28223 dot 54648 dot stgit at host1 dot jankratochvil dot net> <20150326205752 dot 28223 dot 24230 dot stgit at host1 dot jankratochvil dot net> <83iodmnc18 dot fsf at gnu dot org> <20150327073333 dot GA28529 at host1 dot jankratochvil dot net>
- Reply-to: Eli Zaretskii <eliz at gnu dot org>
> Date: Fri, 27 Mar 2015 08:33:33 +0100
> From: Jan Kratochvil <jan.kratochvil@redhat.com>
> Cc: gdb-patches@sourceware.org, pmuldoon@redhat.com
>
> On Fri, 27 Mar 2015 08:18:43 +0100, Eli Zaretskii wrote:
> > I suggest a different name for this command. Unfortunately, "eval" is
> > already taken, but perhaps "parse" or "parse-eval"? Or maybe a new
> > switch to "print"? "compile print" sounds awkward and unintuitive to
> > me.
>
> FYI there is already "compile code" and "compile file".
Yes, I know. But this command is different AFAIU: it doesn't compile
any code at all. So prefixing it with "compile" doesn't sound right
to me.