Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Nick Roberts <nickrob@snap.net.nz>
To: Vladimir Prus <ghost@cs.msu.su>
Cc: gdb-patches@sources.redhat.com
Subject: Re: CLI and GDB/MI documentation patch
Date: Fri, 12 May 2006 12:44:00 -0000	[thread overview]
Message-ID: <17509.54397.736467.479414@kahikatea.snap.net.nz> (raw)


> I'd agree with Eli that the proposed text sounds a bit like history, but it
> documents some important points:

I'm not sure I like it because:

> - That you can type CLI commands into MI, and this is not longer considered
>   to work just by accident

It was never just by accident, just more of a hack.

> - That typing CLI command has the same effect as -interpreter-exec console

Its not quite the same, the latter goes through mi_cmd_execute but the
former doesn't.

> - That CLI command don't produce async notifications

They don't *currently* produce async notifications but I'm trying to change
that with my branch.

> Those points are important to have documented, IMO.

Putting these things in the manual just makes it harder to change GDB.
I would rather say: "Its there.  Use it at your own risk".  Or at least:


  For the developers convenience CLI commands can be entered directly.
  However this feature may be removed at some stage in the future and
  it is recommended that front ends use the @code{-interpreter exec} command.
  @xref{GDB/MI Miscellaneous Commands}.




-- 
Nick                                           http://www.inet.net.nz/~nickrob


             reply	other threads:[~2006-05-12 12:44 UTC|newest]

Thread overview: 47+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-05-12 12:44 Nick Roberts [this message]
2006-05-12 14:19 ` Eli Zaretskii
2006-05-12 16:42   ` Bob Rossi
2006-05-12 22:14   ` Nick Roberts
2006-05-12 22:19     ` Bob Rossi
2006-05-13  9:13       ` Nick Roberts
2006-05-13 16:04         ` Daniel Jacobowitz
2006-05-30 15:59           ` {PATCH] MI Doco [was Re: CLI and GDB/MI...] Nick Roberts
2006-05-31  1:20             ` Eli Zaretskii
2006-05-31  3:15               ` Nick Roberts
2006-05-31 13:02                 ` Eli Zaretskii
2006-05-31 22:04                   ` Nick Roberts
2006-05-31 23:17                 ` Daniel Jacobowitz
2006-06-01  7:24                   ` Eli Zaretskii
2006-06-01 13:09                     ` Daniel Jacobowitz
2006-05-31 15:33             ` Bob Rossi
2006-05-31 22:11               ` Nick Roberts
  -- strict thread matches above, loose matches on Subject: below --
2006-05-12  1:16 CLI and GDB/MI documentation patch Bob Rossi
2006-05-12  7:53 ` Eli Zaretskii
2006-05-12  8:14   ` Vladimir Prus
2006-05-12 11:30     ` Eli Zaretskii
2006-05-12 13:56       ` Bob Rossi
2006-05-12 12:49   ` Daniel Jacobowitz
2006-05-12 12:54     ` Daniel Jacobowitz
2006-05-12 13:58     ` Eli Zaretskii
2006-05-12 14:02       ` Daniel Jacobowitz
2006-05-12 14:10         ` Bob Rossi
2006-05-12 18:32           ` Eli Zaretskii
2006-05-12 18:37         ` Eli Zaretskii
2006-05-12 18:55           ` Daniel Jacobowitz
2006-05-12 19:01             ` Eli Zaretskii
2006-05-12 19:16               ` Daniel Jacobowitz
2006-05-12 19:51                 ` Bob Rossi
2006-05-13  9:28                 ` Eli Zaretskii
2006-05-15 15:50                   ` Daniel Jacobowitz
2006-05-12 20:26               ` PAUL GILLIAM
2006-05-13  8:45                 ` Eli Zaretskii
2006-05-12 12:59   ` Bob Rossi
2006-05-12 14:12     ` Eli Zaretskii
2006-05-12 14:30       ` Bob Rossi
2006-05-12 18:28         ` Eli Zaretskii
2006-05-12 19:19           ` Bob Rossi
2006-05-13  8:09             ` Eli Zaretskii
2006-05-13 11:02               ` Bob Rossi
2006-05-13 14:29                 ` Eli Zaretskii
2006-05-29 19:05           ` Bob Rossi
2006-05-30  7:17             ` 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=17509.54397.736467.479414@kahikatea.snap.net.nz \
    --to=nickrob@snap.net.nz \
    --cc=gdb-patches@sources.redhat.com \
    --cc=ghost@cs.msu.su \
    /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