From: Sami Wagiaalla <swagiaal@redhat.com>
To: Stan Cox <scox@redhat.com>
Cc: Nurdin Premji <npremji@redhat.com>, Frysk List <frysk@sourceware.org>
Subject: Re: frysk.rt.Frame and frysk.debuginfo.DebugInfo
Date: Thu, 07 Jun 2007 14:54:00 -0000 [thread overview]
Message-ID: <46680850.4050000@redhat.com> (raw)
In-Reply-To: <1181166384.3102.313.camel@multics.rdu.redhat.com>
> So we need to come up with a
> way to have a single shared DebugInfo.
>
Factories are a common way of solving this problem. Make the constructor
of DebugInfo private and DebugInfo objects can only be created through a
DebugInfoFactory which keeps a cache of DebugInfo objects.
DebugInfoFactory would take a frame, check the cache and return a
DebugInfo object.
This by the way also solves the antlr problem. If there is a DebugInfo
object per frame, then antlr objects called from within that DebugInfo
object are only concered with that objects Frame.
Sami Wagiaalla
prev parent reply other threads:[~2007-06-07 13:30 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-06-07 13:13 Stan Cox
2007-06-07 13:30 ` Stan Cox
2007-06-07 14:54 ` Sami Wagiaalla [this message]
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=46680850.4050000@redhat.com \
--to=swagiaal@redhat.com \
--cc=frysk@sourceware.org \
--cc=npremji@redhat.com \
--cc=scox@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).