From: Paul Hilfinger <hilfingr@EECS.Berkeley.EDU>
To: Daniel Jacobowitz <drow@false.org>
Cc: Joel Brobecker <brobecker@adacore.com>, gdb-patches@sourceware.org
Subject: Re: generic code duplication in Ada files
Date: Tue, 29 Jan 2008 23:53:00 -0000 [thread overview]
Message-ID: <200801292349.m0TNnVaV025063@tully.CS.Berkeley.EDU> (raw)
In-Reply-To: Your message of Tue, 29 Jan 2008 17:41:23 -0500. <20080129224123.GA6586@caradoc.them.org>
> Some of the things in Ada-specific code will be a mess to get into
> common code, but IMO clearly worthwhile. For instance, a version of
> symbol lookup which can return more than one symbol.
I am glad to hear you say that. Our original reason for this
duplication, as you probably guessed, was to avoid disturbing core GDB
"merely" for the sake of accommodating a less-familiar language. Our
assumption was that any major maintenance headaches that resulted
would be our problem. But apart from this political motivation, a
major refactoring at this point would clearly be beneficial.
Paul Hilfinger
next prev parent reply other threads:[~2008-01-29 23:50 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-01-29 22:41 Joel Brobecker
2008-01-29 22:51 ` Daniel Jacobowitz
2008-01-29 23:53 ` Paul Hilfinger [this message]
2008-01-30 11:39 ` Pierre Muller
2008-01-30 18:50 ` Joel Brobecker
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=200801292349.m0TNnVaV025063@tully.CS.Berkeley.EDU \
--to=hilfingr@eecs.berkeley.edu \
--cc=Hilfinger@CS.Berkeley.EDU \
--cc=brobecker@adacore.com \
--cc=drow@false.org \
--cc=gdb-patches@sourceware.org \
/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