From: Adam Jocksch <ajocksch@redhat.com>
To: Sami Wagiaalla <swagiaal@redhat.com>
Cc: frysk <frysk@sourceware.org>
Subject: Re: Proposed frysk.rt.Display
Date: Wed, 09 May 2007 18:47:00 -0000 [thread overview]
Message-ID: <464216C7.10503@redhat.com> (raw)
In-Reply-To: <464214BD.2010908@redhat.com>
Sami Wagiaalla wrote:
> Can you provide more context here please.
> What is the problem the proposed Display object is solving ?
>
The problem is that a Variable object has no concept of when it is in or
out of scope, as well as when it changes from being in memory to being
in a register. The Display class will act as a sort of intermediary
between Variable and classes that wish to access Variables (such as
variable watches in the source window), such that they will not need to
worry about checking whether the variable is still in scope, in memory
or in a register, etc.
next prev parent reply other threads:[~2007-05-09 18:45 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-05-09 18:36 Adam Jocksch
2007-05-09 18:45 ` Sami Wagiaalla
2007-05-09 18:47 ` Adam Jocksch [this message]
2007-05-10 15:23 ` Sami Wagiaalla
2007-05-10 18:38 ` Andrew Cagney
2007-05-11 13:44 ` Stan Cox
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=464216C7.10503@redhat.com \
--to=ajocksch@redhat.com \
--cc=frysk@sourceware.org \
--cc=swagiaal@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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).