From: Michael Snyder <msnyder@redhat.com>
To: Eli Zaretskii <eliz@gnu.org>
Cc: gdb-patches@sources.redhat.com
Subject: Re: [RFA] Add new command class_experimental
Date: Fri, 18 Nov 2005 21:41:00 -0000 [thread overview]
Message-ID: <437E4335.2090509@redhat.com> (raw)
In-Reply-To: <u1x1disd5.fsf@gnu.org>
Eli Zaretskii wrote:
>>Date: Fri, 18 Nov 2005 12:25:46 -0800
>>From: Michael Snyder <msnyder@redhat.com>
>>
>>This is to add a new category of gdb commands, "experimental".
>>These will be explicitly "use at your own risk", and gdb will
>>tell you so.
>
>
> Hmm... I'm not sure I like this idea. Why not add these as normal
> commands? If it's useful and stable enough, people will use it. As
> for possible bugs, the non-experimental stuff has those too.
Well, because we *don't* regard it as stable. Still using
the rcore command as the canonical example, it's highly
experimental, nowhere near "finished", and we can't even
characterize when it will work, and when it won't. I
would not feel comfortable inviting an unsophisticated
user to use it, and I wouldn't want to take on the task
of explaining to an unsophisticated user the circumstances
under which it might or might not be safe to use.
I think of this as a compromise, to encourage collaborative
development. Of course I'm willing to just leave the rcore
command out there as a patch, but I figured there could easily
be other features like it, that we might want to "try out"
without implying that they are generally safe, stable, or
"finished".
next prev parent reply other threads:[~2005-11-18 21:10 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-11-18 21:35 Michael Snyder
2005-11-18 21:36 ` Eli Zaretskii
2005-11-18 21:41 ` Michael Snyder [this message]
2005-11-19 1:17 ` Eli Zaretskii
2005-11-19 1:21 ` Michael Snyder
2005-11-19 1:22 ` Eli Zaretskii
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=437E4335.2090509@redhat.com \
--to=msnyder@redhat.com \
--cc=eliz@gnu.org \
--cc=gdb-patches@sources.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