From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 30111 invoked by alias); 9 May 2007 18:01:36 -0000 Received: (qmail 30101 invoked by uid 22791); 9 May 2007 18:01:35 -0000 X-Spam-Status: No, hits=-1.4 required=5.0 tests=AWL,BAYES_50,SPF_HELO_PASS,SPF_PASS X-Spam-Check-By: sourceware.org Received: from mx1.redhat.com (HELO mx1.redhat.com) (66.187.233.31) by sourceware.org (qpsmtpd/0.31) with ESMTP; Wed, 09 May 2007 18:01:32 +0000 Received: from int-mx1.corp.redhat.com (int-mx1.corp.redhat.com [172.16.52.254]) by mx1.redhat.com (8.13.1/8.13.1) with ESMTP id l49I1R2A006765 for ; Wed, 9 May 2007 14:01:27 -0400 Received: from pobox.toronto.redhat.com (pobox.toronto.redhat.com [172.16.14.4]) by int-mx1.corp.redhat.com (8.13.1/8.13.1) with ESMTP id l49I1RcU013807 for ; Wed, 9 May 2007 14:01:27 -0400 Received: from [10.11.14.37] (vpn-14-37.rdu.redhat.com [10.11.14.37]) by pobox.toronto.redhat.com (8.12.11.20060308/8.12.11) with ESMTP id l49I1QKI021039 for ; Wed, 9 May 2007 14:01:26 -0400 Message-ID: <46420C75.6040401@redhat.com> Date: Wed, 09 May 2007 18:36:00 -0000 From: Adam Jocksch User-Agent: Thunderbird 1.5.0.10 (X11/20070306) MIME-Version: 1.0 To: frysk Subject: Proposed frysk.rt.Display Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-IsSubscribed: yes Mailing-List: contact frysk-help@sourceware.org; run by ezmlm Precedence: bulk List-Id: List-Subscribe: List-Post: List-Help: , Sender: frysk-owner@sourceware.org X-SW-Source: 2007-q2/txt/msg00136.txt.bz2 From a discussion with Andrew: > What is needed here is a higher level abstraction, a frysk.rt.Display (I'm not using Watch as that implies hardware > WatchPoint) object, say, that worries about scope rules, and changing location, and being able to save/restore > itself. The display object, when the program stops, would know to re-instantiate the underlying Variable (if still in > scope) when the process stops. So, mulling it over it sounds like frysk.rt.Display needs to have the following - an isInScope() method or something akin to it in functionality - some reference to the Variable itself. I'm guess that something like private Variable myVar is probably not what's needed here; so should we be storing the variable's Location? or the higher level source#line#col? - all of the value-access functionality already implemented in Variable (or a way to get a Variable from a Display, then call get Int or whatever on it) The second point is probably the trickiest one, and the point where I have the least idea of what would be sufficient/best. Adam