From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 4363 invoked by alias); 22 Oct 2006 09:11:14 -0000 Received: (qmail 4339 invoked by uid 22791); 22 Oct 2006 09:11:13 -0000 X-Spam-Check-By: sourceware.org Received: from smtp10.hccnet.nl (HELO smtp10.hccnet.nl) (62.251.0.13) by sourceware.org (qpsmtpd/0.31) with ESMTP; Sun, 22 Oct 2006 09:11:11 +0000 Received: from [192.168.0.151] by smtp10.hccnet.nl via [80.100.236.49] with ESMTP id k9M9B5OH010063 (8.13.6/2.05); Sun, 22 Oct 2006 11:11:05 +0200 (MET DST) Message-ID: <453B35A8.30403@hccnet.nl> Date: Sun, 22 Oct 2006 09:11:00 -0000 From: Erik Leunissen User-Agent: Thunderbird 1.5 (X11/20051201) MIME-Version: 1.0 To: Eli Zaretskii , gdb@sourceware.org Subject: Re: breakpoint for accessing memory location References: <4537DBC6.1030807@hccnet.nl> <20061019201214.GA32332@nevyn.them.org> <4537DEDC.5000008@hccnet.nl> <4538FF9D.9070803@hccnet.nl> <453A9EE4.1070800@hccnet.nl> In-Reply-To: Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Virus-Status: Clean X-IsSubscribed: yes Mailing-List: contact gdb-help@sourceware.org; run by ezmlm Precedence: bulk List-Subscribe: List-Archive: List-Post: List-Help: , Sender: gdb-owner@sourceware.org X-SW-Source: 2006-10/txt/msg00190.txt.bz2 Eli Zaretskii wrote: > > Well, yes, but how far should we go in explaining the semantics of > programming languages? I mean, isn't it common knowledge that the > name of a variable stands for its value? When the manual says ``the > value of a variable'', what could the reader possibly think of except > the variable's name? > True, if C is the sole perspective. If so please disregard. My remark stems from experience with dynamic programming languages. In that area, separate methods exist to programmatically refer to the name of a variable and to its value (Tcl example appended). So, it depends on your background I suppose. And mine may be odd. Also, it may be ineffective to consider from where people may enter the debugging arena (or C arena). I leave this entirely to your judgement. Regardless, I'm already very pleased with the explanation as it is now. Thanks, Erik ==== Interactive Tcl example (I guess Python and Perl show similar behaviour): % set variableName 34 34 % puts $variableName 34 % puts variableName variableName == end of post ==