Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Andrew Cagney <ac131313@cygnus.com>
To: Kevin Buettner <kevinb@cygnus.com>
Cc: Elena Zannoni <ezannoni@cygnus.com>, gdb-patches@sources.redhat.com
Subject: Re: [PATCH] xcoffread.c: remove include of partial-stab.h
Date: Mon, 01 Oct 2001 15:42:00 -0000	[thread overview]
Message-ID: <3BB8F15A.9060300@cygnus.com> (raw)
In-Reply-To: <1011001210800.ZM19181@ocotillo.lan>

> I know this file has no official maintainer, but I'll wait a few days
>> to check it in anyway.
> 
> 
> I've looked this patch over.  I've verified that only two cases of
> partial-stab.h were needed by xcoffread.c.  Also, it appears to me
> that you've correctly integrated the two necessary cases into
> xcoffread.c.
> 
> My only concern about this patch is with the duplication of the two
> cases in xcoffread.c.  These hunks of code are of substantial size and
> it occurs to me that correct maintenance of this code may require
> keeping the various copies in sync.  I'm wondering if it'd be possible
> to turn these hunks of code into functions.  That way we might be able
> to avoid duplicating (some of) this code in three different places.

I think pragmatism being applied to this patch should be the same as for 
the aout vs svr4 solib code.

Yes in theory, there is common code that could be abstracted out.  In 
reality, I think there is zero benefit.  Instead all the xcoffread stuff 
can be confined to a single file where it can be ignored (and hopefully 
eventually deleted).

enjoy,
Andrew



  parent reply	other threads:[~2001-10-01 15:42 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-09-30 14:01 Elena Zannoni
2001-10-01 13:11 ` Andrew Cagney
2001-10-01 14:08 ` Kevin Buettner
2001-10-01 14:29   ` Elena Zannoni
2001-10-01 15:26     ` Kevin Buettner
2001-10-01 15:42   ` Andrew Cagney [this message]
2001-10-01 19:40 ` Elena Zannoni

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=3BB8F15A.9060300@cygnus.com \
    --to=ac131313@cygnus.com \
    --cc=ezannoni@cygnus.com \
    --cc=gdb-patches@sources.redhat.com \
    --cc=kevinb@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