From: Andrew Cagney <ac131313@ges.redhat.com>
To: Daniel Jacobowitz <drow@mvista.com>
Cc: gdb-patches@sources.redhat.com
Subject: Re: [RFA] convert blocks to dictionaries, phase 1, main part
Date: Tue, 17 Sep 2002 09:03:00 -0000 [thread overview]
Message-ID: <3D875236.3060100@ges.redhat.com> (raw)
In-Reply-To: <20020917143553.GA28408@nevyn.them.org>
> On Mon, Sep 16, 2002 at 03:25:53PM -0700, David Carlton wrote:
>
>> This is the first of three patches that will begin the process of
>> converting blocks to do variable lookup via dictionaries. (Which are
>> what I'd been calling environments until Andrew noted that that
>> clashed with the existing 'struct environ'.)
>>
>> The goal of these three patches it to make sure that all blocks that
>> are created have a 'dict' member. Once these patches are applied, it
>> will be possible to lookup variables either using the old methods
>> (BLOCK_SYM, etc.) or using the new dictionary methods. Phase 2 will
>> then convert all accessors over to using th new dictionary methods;
>> phase 3 will get rid of the old methods so that the new dictionary
>> methods get used exclusively.
>
>
> David,
>
> I've only skimmed this, but it looks nice. I think that you should
> take Andrew's suggestion, though - create a branch to finish this work
> on. It's a bit of a hassle, since you'll need to do periodic merges to
> the branch, but I don't feel right adding something with this many
> temporary interfaces and FIXMEs to the trunk. Then you can commit
> patches on the branch without approval, and get it into a stabler
> state.
It will still need a general thumbs up, but at least the maintainer will
have the confidence of knowing that it really does work.
cf the recent problem with ranges.
Andrew
next prev parent reply other threads:[~2002-09-17 16:03 UTC|newest]
Thread overview: 33+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-09-16 15:26 David Carlton
2002-09-16 15:30 ` David Carlton
2002-09-17 7:35 ` Daniel Jacobowitz
2002-09-17 9:03 ` Andrew Cagney [this message]
2002-09-17 10:43 ` David Carlton
2002-09-17 10:49 ` Daniel Jacobowitz
2002-09-17 11:34 ` David Carlton
2002-09-17 12:24 ` Andrew Cagney
2002-09-17 11:44 ` Andrew Cagney
2002-09-17 12:30 ` Daniel Jacobowitz
2002-09-17 12:49 ` Andrew Cagney
2002-09-17 13:32 ` Daniel Jacobowitz
2002-09-17 21:48 ` Daniel Berlin
2002-09-18 7:26 ` Andrew Cagney
2002-09-20 9:13 ` Jim Blandy
2002-09-17 12:59 ` Daniel Berlin
2002-09-17 13:13 ` Andrew Cagney
2002-09-17 9:29 ` Andrew Cagney
2002-09-17 11:04 ` David Carlton
2002-09-17 12:16 ` Andrew Cagney
2002-09-17 12:35 ` Daniel Jacobowitz
2002-09-17 12:46 ` David Carlton
2002-09-17 12:57 ` Andrew Cagney
2002-09-22 14:51 ` Jim Blandy
2002-09-17 12:54 ` Michael Snyder
2002-09-17 12:59 ` Daniel Berlin
2002-09-18 2:56 ` Richard Earnshaw
2002-09-18 14:07 ` Andrew Cagney
2002-09-19 3:14 ` Richard Earnshaw
2002-09-19 6:18 ` Elena Zannoni
2002-09-19 7:52 ` Richard Earnshaw
2002-09-19 7:51 ` Andrew Cagney
2002-09-22 14:41 ` Jim Blandy
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=3D875236.3060100@ges.redhat.com \
--to=ac131313@ges.redhat.com \
--cc=drow@mvista.com \
--cc=gdb-patches@sources.redhat.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