Mirror of the gdb mailing list
 help / color / mirror / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: Michael Snyder <msnyder@redhat.com>
Cc: gdb@sources.redhat.com, jrydberg@virtutech.com, fche@redhat.com,
	        brolley@redhat.com, ebachalo@redhat.com
Subject: Re: Return to Reverse Execution
Date: Fri, 06 Jan 2006 09:02:00 -0000	[thread overview]
Message-ID: <ufyo1ivax.fsf@gnu.org> (raw)
In-Reply-To: <43BDF1D6.1040807@redhat.com> (message from Michael Snyder on 	Thu, 05 Jan 2006 20:28:06 -0800)

> Date: Thu, 05 Jan 2006 20:28:06 -0800
> From: Michael Snyder <msnyder@redhat.com>
> CC: gdb@sources.redhat.com, jrydberg@virtutech.com, fche@redhat.com,         brolley@redhat.com, ebachalo@redhat.com
> 
> > May I raise again the issue of names?  That is, could we please
> > consider
> > 
> > 	back-step
> > 	previous
> > 	back-continue
> > 	back-finish
> > 
> > ?  I think ``reverse'' is ambiguous: it doesn't actually say that we
> > are going backwards, just that we are reversing the direction, like
> > some kind of toggle.  Reverse would be okay if we had some global
> > direction flag which ``reverse'' command would reverse.  This is not
> > the case: these commands will _always_ go backwards, even if we
> > implement exec-direction and the user sets it to `backward'.
> 
> Eli, I'm certainly willing to consider it, but as I review the
> previous discussion, it seems like you were the only proponant
> of these names.

That might be so, but please note that you yourself used ``back'' and
``backward'' in almost every other place in your description except
the command names.  Doesn't this tell you something?


  reply	other threads:[~2006-01-06  9:02 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-01-04 21:01 Michael Snyder
2006-01-05  5:04 ` Eli Zaretskii
2006-01-06  4:28   ` Michael Snyder
2006-01-06  9:02     ` Eli Zaretskii [this message]
2006-01-06 15:19       ` Paul Koning
2006-01-13 16:02         ` Bob Rossi
2006-01-13 19:43           ` Eli Zaretskii
2006-01-06 10:30     ` Dave Korn
2006-01-06 11:17       ` Eli Zaretskii
2006-01-06 12:29         ` Dave Korn
2006-01-06 14:09           ` Eli Zaretskii
2006-01-06 14:12           ` Eli Zaretskii
2006-01-06 16:59           ` Dave Brolley
2006-01-06 19:57 ` Daniel Jacobowitz
2006-01-06 21:51   ` Paul Gilliam
2006-01-06 21:53     ` Daniel Jacobowitz
2006-01-06 22:05       ` Paul Gilliam
2006-01-09  8:41 ` Vladimir Prus
2006-05-16 20:24 ` Julian Smith

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=ufyo1ivax.fsf@gnu.org \
    --to=eliz@gnu.org \
    --cc=brolley@redhat.com \
    --cc=ebachalo@redhat.com \
    --cc=fche@redhat.com \
    --cc=gdb@sources.redhat.com \
    --cc=jrydberg@virtutech.com \
    --cc=msnyder@redhat.com \
    /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