From: Sami Wagiaalla <swagiaal@redhat.com>
To: frysk <frysk@sources.redhat.com>
Subject: ValueFactory
Date: Fri, 01 Jun 2007 15:51:00 -0000 [thread overview]
Message-ID: <46603AE0.2020201@redhat.com> (raw)
Okay so here is a skeleton:
// this takes care of the creation of Value object
public class ValueFactory{
public static ValueFactory getFactory(Proc){
// check cache and return a ValueFactory
}
private ValueFactory(Proc proc){
}
public Value getValue(String name, Frame currentFrame){
...
}
public Value getValue(DwarfDie die){
...
}
}
// this is just speculation but can be put either in Value it self or in
a ValuePrint object
...
public String printValue(Value value){
}
...
How well will the above work for hpd, stack examination, source window,
DisplayVariable, an any other interested parties :)
Sami
next reply other threads:[~2007-06-01 15:27 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-06-01 15:51 Sami Wagiaalla [this message]
2007-06-01 16:17 ` ValueFactory Adam Jocksch
2007-06-01 19:05 ` ValueFactory Andrew Cagney
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=46603AE0.2020201@redhat.com \
--to=swagiaal@redhat.com \
--cc=frysk@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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).