Mirror of the gdb mailing list
 help / color / mirror / Atom feed
From: Daniel Jacobowitz <drow@mvista.com>
To: David Carlton <carlton@math.stanford.edu>
Cc: Jim Blandy <jimb@redhat.com>, gdb@sources.redhat.com
Subject: Re: suggestion for dictionary representation
Date: Mon, 23 Sep 2002 18:28:00 -0000	[thread overview]
Message-ID: <20020924012827.GB11065@nevyn.them.org> (raw)
In-Reply-To: <ro1k7lcsj0x.fsf@jackfruit.Stanford.EDU>

On Mon, Sep 23, 2002 at 10:38:54AM -0700, David Carlton wrote:
> On Sun, 22 Sep 2002 23:10:56 -0400, Daniel Jacobowitz <drow@mvista.com> said:
> > I'm tempted to whack the block special case for function arguments.  It
> > may make name lookup a little more complicated but I think it will make
> > everything clearer.  We could, of course, try this on the branch and
> > see if we like the results :)
> 
> Would it be reasonable to break up function blocks into two separate
> blocks: a linear block that only defines the parameters for the
> function and a non-linear block that contains the actual local
> variables?  Not that I think Jim's scheme is a bad one - I agree that
> it's better than the current scheme - but given the possibility of
> local variables shadowing function parameters, it seems to me to be
> conceptually cleaner to have two separate blocks appear anyways, and
> it also solves this problem.

Absolutely, I think it would be reasonable.  In fact I think it's a
really good idea.

> Also, for what it's worth, I'm still not ready to completely give up
> on representing members of classes via a dictionary; that would
> provide another place where a linear dictionary environment could be
> useful.

I wouldn't mind having the function arguments be a dictionary,
either...

-- 
Daniel Jacobowitz
MontaVista Software                         Debian GNU/Linux Developer


  parent reply	other threads:[~2002-09-24  1:28 UTC|newest]

Thread overview: 28+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-09-22 19:59 Jim Blandy
2002-09-22 20:11 ` Daniel Jacobowitz
2002-09-23 10:38   ` David Carlton
2002-09-23 17:34     ` Daniel Berlin
2002-09-23 18:39       ` Daniel Jacobowitz
2002-09-23 21:28         ` Daniel Berlin
2002-09-23 21:38           ` Eli Zaretskii
2002-09-23 21:44             ` Daniel Berlin
2002-09-23 21:47               ` Eli Zaretskii
2002-09-23 21:54                 ` Daniel Berlin
2002-09-24  9:33       ` David Carlton
2002-09-24 10:42         ` Daniel Berlin
2002-09-24 10:53           ` David Carlton
2002-09-24 20:01         ` Jim Blandy
2002-09-24 20:50           ` Daniel Berlin
2002-09-23 18:28     ` Daniel Jacobowitz [this message]
2002-09-24  3:51     ` Paul N. Hilfinger
2002-09-24 19:52     ` Jim Blandy
2002-09-24 20:37       ` Elena Zannoni
2002-09-24 20:53       ` Daniel Berlin
2002-09-23 23:50 Jim Blandy
2002-09-24  6:19 ` Daniel Berlin
2002-09-24  7:06   ` Daniel Jacobowitz
2002-09-24 21:01   ` Jim Blandy
2002-09-25  5:54     ` Daniel Jacobowitz
2002-09-27 11:23       ` Jim Blandy
2002-09-27 11:28         ` Daniel Jacobowitz
2002-09-24  9:49 ` David Carlton

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=20020924012827.GB11065@nevyn.them.org \
    --to=drow@mvista.com \
    --cc=carlton@math.stanford.edu \
    --cc=gdb@sources.redhat.com \
    --cc=jimb@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