From: Eli Zaretskii <eliz@gnu.org>
To: Vladimir Prus <ghost@cs.msu.su>
Cc: gdb-patches@sources.redhat.com
Subject: Re: [RFA] Document fixed/floating variable objects and thread-id.
Date: Wed, 09 Apr 2008 15:21:00 -0000 [thread overview]
Message-ID: <u3apvax9v.fsf@gnu.org> (raw)
In-Reply-To: <ftib2h$6ue$1@ger.gmane.org>
> From: Vladimir Prus <ghost@cs.msu.su>
> Date: Wed, 09 Apr 2008 15:59:14 +0400
>
> >> +fixed variable object, the expression is parsed when the variable
> >> +object is created, including associating indentifiers to specific
> >> +variables. The meaning of expression never changes. A floating
> >> +variable object has its expression reparsed each time the variable
> >> +object is updated. In particular, the meaning of identifiers can
> >> +change every time.
> >
> > Instead of ``meaning'' here, isn't it better to say ``value''?
>
> Identifier does not have a value. Think of 'i' -- it's just a name.
> It is then associated to a specific variable, which variable has value.
> What I mean is that association between identifiers to variables can
> change for floating variable objects. Of course, the values can also
> change, but values can change even for fixed variable objects.
>
> What's the best way to express this?
I don't know yet: what is an ``identifier'' in this context? You
don't mean symbols in the source language of the program being
debugged, as in your example with `i', do you?
next prev parent reply other threads:[~2008-04-09 15:01 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-04-04 9:32 Vladimir Prus
2008-04-04 11:47 ` Eli Zaretskii
2008-04-09 13:49 ` Vladimir Prus
2008-04-09 15:21 ` Eli Zaretskii [this message]
2008-04-09 17:06 ` Vladimir Prus
2008-04-09 18:04 ` Eli Zaretskii
2008-04-09 20:37 ` Vladimir Prus
2008-04-09 21:25 ` Eli Zaretskii
2008-04-09 22:17 ` Vladimir Prus
2008-04-23 11:52 ` Vladimir Prus
2008-04-23 18:00 ` Eli Zaretskii
2008-04-26 17:44 ` Vladimir Prus
2008-04-26 18:45 ` Eli Zaretskii
2008-04-04 13:08 ` Daniel Jacobowitz
2008-04-04 13:44 ` Pedro Alves
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=u3apvax9v.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=gdb-patches@sources.redhat.com \
--cc=ghost@cs.msu.su \
/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