Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Elena Zannoni <ezannoni@redhat.com>
To: David Carlton <carlton@math.stanford.edu>
Cc: Elena Zannoni <ezannoni@redhat.com>, gdb-patches@sources.redhat.com
Subject: Re: [rfa] language hooks for lookup_symbol
Date: Mon, 19 May 2003 19:52:00 -0000	[thread overview]
Message-ID: <16073.14152.971677.974225@localhost.redhat.com> (raw)
In-Reply-To: <ro1u1bqg2q9.fsf@jackfruit.Stanford.EDU>

David Carlton writes:
 > On Mon, 19 May 2003 11:19:50 -0400, Elena Zannoni <ezannoni@redhat.com> said:
 > 
 > > 1. check in the if0 elimination by itself, then the deletion of
 > >    static_block parameter and teh addition of the block_static_bloc
 > >    function. After that check in the rest (which is really the big change).
 > 
 > Will do.
 > 
 > > 2. I think that instead of: int la_lookup_symbol_this; We can just
 > >      have the new field be a function pointer to NULL or to the
 > >      value_of_this function itself. This function itself can be split
 > >      in 2, one for objc and one for c++.
 > 
 > That makes sense.  I'll also add a FIXME comment saying that we should
 > audit all existing languages to make sure that the field is set
 > properly.
 > 
 > > 3. move the comments as well, instead of deleting them.
 > 
 > I assume you're referring to these comments?
 > 
 > -  /* NOTE: carlton/2002-12-05: There is a question as to whether or
 > -     not it would be appropriate to search the current global block
 > -     here as well.  (That's what this code used to do before the
 > -     is_a_field_of_this check was moved up.)  On the one hand, it's
 > -     redundant with the lookup_symbol_aux_symtabs search that happens
 > -     next.  On the other hand, if decode_line_1 is passed an argument
 > -     like filename:var, then the user presumably wants 'var' to be
 > -     searched for in filename.  On the third hand, there shouldn't be
 > -     multiple global variables all of which are named 'var', and it's
 > -     not like decode_line_1 has ever restricted its search to only
 > -     global variables in a single filename.  All in all, only
 > -     searching the static block here seems best: it's correct and it's
 > -     cleanest.  */
 > -
 > -  /* NOTE: carlton/2002-12-05: There's also a possible performance
 > -     issue here: if you usually search for global symbols in the
 > -     current file, then it would be slightly better to search the
 > -     current global block before searching all the symtabs.  But there
 > -     are other factors that have a much greater effect on performance
 > -     than that one, so I don't think we should worry about that for
 > -     now.  */
 > -
 > 
 > The reason why I was planning to delete them is because they don't
 > make a lot of sense after this latest reorganization (since the "this
 > code" and the "is_a_field_of_this" mention wouldn't refer to the
 > function in question) and because I'm no longer bothered by the qualms
 > that led me to write the comments in the first place.  But if you want
 > me to keep them, I will (adding another note that they've been moved).

If it makes more sense, just rephrase them as you see appropriate.

elena


 > 
 > David Carlton
 > carlton@math.stanford.edu


  reply	other threads:[~2003-05-19 19:52 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-05-18 22:47 David Carlton
2003-05-19 15:14 ` Elena Zannoni
2003-05-19 19:23   ` David Carlton
2003-05-19 19:52     ` Elena Zannoni [this message]
2003-05-20  2:01   ` 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=16073.14152.971677.974225@localhost.redhat.com \
    --to=ezannoni@redhat.com \
    --cc=carlton@math.stanford.edu \
    --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