From: Joel Brobecker <brobecker@adacore.com>
To: Ulrich Weigand <uweigand@de.ibm.com>
Cc: gdb-patches@sourceware.org
Subject: Re: [RFC] Reducing the use of current_language - some patches
Date: Mon, 05 Nov 2007 03:50:00 -0000 [thread overview]
Message-ID: <20071105035014.GA3911@adacore.com> (raw)
In-Reply-To: <200711041715.lA4HF0JL026952@d12av02.megacenter.de.ibm.com>
Hey Ulrich,
> So I was wondering if we shouldn't add just a "language" parameter
> to the parsing routines, but something more general, like a "parse
> context" structure. This could encapsulate all that global state,
> and would be easily extensible in the future ...
Thanks for your feedback. Indeed, I had completely forgotten about
the input radix, and it should indeed be passed. Having a structure
is a really good idea.
On the other hand, I'm not sure we're ready to have the parse context
contain the gdbarch. For instance, the breakpoint structure doesn't
save it, so we don't have access to it when we want to re_set the
breakpoint.
I propose we start with just the language and the input radix for
this task, and then we can think about incorporating the gdbarch.
> Maybe (if this is a good idea), it could be done after your current
> set of patches; on the other hand, as you're touching all those files
> anyway, maybe it would be simpler to do it in one go.
It would actually be simpler for me to do the work in two phases,
since I'm almost done with the first phase. Now, I have to redo
probably most of it. However, I will do it in one go as it will
create less work for the insight guys, as they will need to update
their sources only once.
Thanks again.
--
Joel
next prev parent reply other threads:[~2007-11-05 3:50 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-10-31 10:47 Joel Brobecker
2007-11-04 17:15 ` Ulrich Weigand
2007-11-05 3:50 ` Joel Brobecker [this message]
2007-11-05 13:19 ` Daniel Jacobowitz
2007-11-05 15:25 ` Ulrich Weigand
2007-11-05 17:18 ` 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=20071105035014.GA3911@adacore.com \
--to=brobecker@adacore.com \
--cc=gdb-patches@sourceware.org \
--cc=uweigand@de.ibm.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