Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Joel Brobecker <brobecker@adacore.com>
To: Vladimir Prus <vladimir@codesourcery.com>
Cc: gdb-patches@sources.redhat.com
Subject: Re: [RFA] Remove simplified_command_loop.
Date: Mon, 10 Mar 2008 18:49:00 -0000	[thread overview]
Message-ID: <20080310184913.GA7603@adacore.com> (raw)
In-Reply-To: <200803102000.57308.vladimir@codesourcery.com>

> I cannot find any use of simplified_command_loop neither in
> gdb proper, nor in gdbtk, from which I conclude this is
> not longer needed. OK?

It appears that this function used to be used in MI (mi-interp.c,
function mi_command_loop), and is no longer used since gdb-6.3,
which was released end of 2004. It's been 3 years, and also it
looks like the event loops between CLI and MI mode have been
better reconciled. So:

> 	* top.c (simplified_command_loop): Remove.

This is OK. 

-- 
Joel


      reply	other threads:[~2008-03-10 18:49 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-03-10 17:01 Vladimir Prus
2008-03-10 18:49 ` Joel Brobecker [this message]

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=20080310184913.GA7603@adacore.com \
    --to=brobecker@adacore.com \
    --cc=gdb-patches@sources.redhat.com \
    --cc=vladimir@codesourcery.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