From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 23400 invoked by alias); 9 May 2007 18:47:57 -0000 Received: (qmail 23392 invoked by uid 22791); 9 May 2007 18:47:56 -0000 X-Spam-Status: No, hits=-1.1 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:47:54 +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 l49IlhEk002111 for ; Wed, 9 May 2007 14:47:43 -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 l49IlhGV032059 for ; Wed, 9 May 2007 14:47:43 -0400 Received: from [172.16.14.55] (toner.toronto.redhat.com [172.16.14.55]) by pobox.toronto.redhat.com (8.12.11.20060308/8.12.11) with ESMTP id l49IlgNX026602; Wed, 9 May 2007 14:47:42 -0400 Message-ID: <4642174E.6020306@redhat.com> Date: Thu, 10 May 2007 15:23:00 -0000 From: Sami Wagiaalla User-Agent: Thunderbird 1.5.0.10 (X11/20070302) MIME-Version: 1.0 To: Adam Jocksch CC: frysk Subject: Re: Proposed frysk.rt.Display References: <46420C75.6040401@redhat.com> <464214BD.2010908@redhat.com> <464216C7.10503@redhat.com> In-Reply-To: <464216C7.10503@redhat.com> 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/msg00139.txt.bz2 > 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. Ah cool... thanx :)