From: Tom Tromey <tromey@redhat.com>
To: Joel Brobecker <brobecker@adacore.com>
Cc: gdb-patches@sourceware.org
Subject: Re: [RFC] allow unqualified function names in linespecs
Date: Tue, 24 Jan 2012 19:17:00 -0000 [thread overview]
Message-ID: <m3mx9cc3pe.fsf@fleche.redhat.com> (raw)
In-Reply-To: <20111221140128.GK23376@adacore.com> (Joel Brobecker's message of "Wed, 21 Dec 2011 18:01:28 +0400")
>>>>> "Joel" == Joel Brobecker <brobecker@adacore.com> writes:
[ oldish thread... ]
Joel> Part of the problem also comes from the fact that C++ and Ada are so
Joel> different, and thus are also often used in very different projects.
Joel> Trying to unify support for both without some kind of abstraction
Joel> layer is very hard. In fact, coming up with that abstraction layer
Joel> is also very hard, as we're finding out.
Totally agreed.
Joel> My goal in the past 10 years, has always been to clean the Ada mode up,
Joel> and all the messes we created. But at the same time, I dont' want that
Joel> work to create more work for me during the periodic merges I make from
Joel> the FSF tree to ours. So, my first goal is to first reconcile AdaCore's
Joel> ada-* files with the ones on the FSF. That's a lot of micro-redesign,
Joel> sometimes, to get things to an acceptable state. The good news is,
Joel> I feel like I am getting really close. And once I'm done, I can start
Joel> the cleanup in earnest.
Joel> There are some thing that I need to accept though: If some things
Joel> are common idioms in Ada, there is now way I am going to be able
Joel> to stop supporting them without losing my job :-). Believe it or not,
Joel> though, I do a fair amount of push back against some of the features
Joel> that get requested internally.
Yeah, I wasn't trying to express any displeasure with you personally.
I hope it didn't come across that way.
I was mostly just expressing a wish for how I would like gdb to be
structured internally in the future. And, FWIW, I think there are
already way, way too many special cases for C++ as well.
Tom
prev parent reply other threads:[~2012-01-24 19:15 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-12-14 14:36 Joel Brobecker
2011-12-20 15:24 ` Tom Tromey
2011-12-21 14:08 ` Joel Brobecker
2011-12-23 10:39 ` [commit/Ada 1/3] New function ada-lang.c:should_use_wild_match Joel Brobecker
2011-12-27 4:27 ` Checked in: " Joel Brobecker
2011-12-23 10:39 ` unqualified function names in linespecs in Ada... (try #2) Joel Brobecker
2011-12-23 10:39 ` [RFA 2/3] Ada: allow unqualified function names in linespecs Joel Brobecker
2012-01-12 3:13 ` Joel Brobecker
2012-01-19 15:40 ` Joel Brobecker
2012-01-24 19:41 ` Tom Tromey
2012-01-26 4:23 ` Joel Brobecker
2012-01-26 10:22 ` Crash regression gdb.cp/no-dmgl-verbose.exp: " Jan Kratochvil
2012-01-26 10:55 ` Jan Kratochvil
2012-01-27 5:15 ` Jan Kratochvil
2012-01-27 5:25 ` Joel Brobecker
2012-01-27 17:09 ` [patch] Fix the 2012-01-26 regression by la_get_symbol_name_match_p [Re: Crash regression gdb.cp/no-dmgl-verbose.exp] Jan Kratochvil
2012-01-27 19:27 ` Joel Brobecker
2012-01-27 20:33 ` [commit] " Jan Kratochvil
2011-12-23 11:01 ` [RFA 3/3] Remove language param from name_matcher in struct quick_symbol_functions Joel Brobecker
2012-01-12 4:30 ` Joel Brobecker
2012-01-19 15:47 ` Joel Brobecker
2012-01-24 19:45 ` Tom Tromey
2012-01-26 4:57 ` Joel Brobecker
2012-01-24 19:17 ` Tom Tromey [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=m3mx9cc3pe.fsf@fleche.redhat.com \
--to=tromey@redhat.com \
--cc=brobecker@adacore.com \
--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