From: Andrew Cagney <ac131313@cygnus.com>
To: Eli Zaretskii <eliz@is.elta.co.il>, gdb-patches@sourceware.cygnus.com
Subject: [rfc] ui_out_is_mi_like_p(); Was: [patch] Add -i=mi0 as an interpreter
Date: Wed, 04 Jul 2001 15:34:00 -0000 [thread overview]
Message-ID: <3B4399D4.1060302@cygnus.com> (raw)
In-Reply-To: <200106190901.MAA07858@is.elta.co.il>
> Most of it is straight forward. The
>> nasty bit is where I s/strcmp/strncmp/ in breakpoint.c and infrun.c.
>
>
> Why can't this strncmp be done in one place and then saved in some
> variable? If you do need to use strncmp all over the place, then I
> can't say I care to see the magical constants "mi" and 2 every time
> you do ;-)
The attached patch replaces:
> ! if (interpreter_p && strncmp (interpreter_p, "mi", 2) == 0)
>
with:
if (ui_out_is_mi_like_p (uiout))
it addresses the immedate concern and creates a name so horrible that no
one will want to use it :-)
Andrew
From dmj+@andrew.cmu.edu Wed Jul 04 15:41:00 2001
From: Daniel Jacobowitz <dmj+@andrew.cmu.edu>
To: Mark Kettenis <kettenis@science.uva.nl>
Cc: gdb-patches@sources.redhat.com
Subject: Re: [RFA] The MIPS/Linux port
Date: Wed, 04 Jul 2001 15:41:00 -0000
Message-id: <20010704154043.A23475@nevyn.them.org>
References: <20010704121952.A17445@nevyn.them.org> <s3izoakgy74.fsf@soliton.wins.uva.nl>
X-SW-Source: 2001-07/msg00067.html
Content-length: 1034
On Wed, Jul 04, 2001 at 11:51:27PM +0200, Mark Kettenis wrote:
> Looks like the MIPS port was started before a bit of reformatting of
> the sources and conversion to ISO C took place. Please
>
> * Format the copyright notice at the beginning of the file as all
> (most of) the other files, for example i386-linux-tdep.c.
>
> * Don't put a start on every line of multi-line comments.
>
> * Put two spaces after a full stop (.) in comments, even at the end
> of the comment. Make the comments full senteces, including a full
> stop at the end of them.
>
> * Wrap long comments.
>
> * Use ISO C prototypes and function definitions, e.g.
>
> int
> get_longjmp_target (CORE_ADDR *pc)
> {
>
> and
>
> static void fetch_core_registers (char *, unsigned, int, CORE_ADDR);
>
> (get rid of PARAMS).
Thanks. I'll do these and repost it.
--
Daniel Jacobowitz Carnegie Mellon University
MontaVista Software Debian GNU/Linux Developer
next prev parent reply other threads:[~2001-07-04 15:34 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-06-18 10:54 Andrew Cagney
2001-06-19 2:00 ` Eli Zaretskii
2001-06-19 12:47 ` Andrew Cagney
2001-07-04 14:03 ` [rfa/doc] Mention -i=mi0; Was: " Andrew Cagney
2001-07-04 23:52 ` Eli Zaretskii
2001-07-05 21:06 ` Andrew Cagney
2001-07-06 1:16 ` Eli Zaretskii
2001-07-04 15:34 ` Andrew Cagney [this message]
2001-07-04 23:53 ` [rfc] ui_out_is_mi_like_p(); " 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=3B4399D4.1060302@cygnus.com \
--to=ac131313@cygnus.com \
--cc=eliz@is.elta.co.il \
--cc=gdb-patches@sourceware.cygnus.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