From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from simark.ca by simark.ca with LMTP id byJmCskfKWHCYAAAWB0awg (envelope-from ) for ; Fri, 27 Aug 2021 13:24:25 -0400 Received: by simark.ca (Postfix, from userid 112) id 1965B1EE1B; Fri, 27 Aug 2021 13:24:25 -0400 (EDT) X-Spam-Checker-Version: SpamAssassin 3.4.2 (2018-09-13) on simark.ca X-Spam-Level: X-Spam-Status: No, score=-0.7 required=5.0 tests=DKIM_SIGNED,DKIM_VALID, DKIM_VALID_AU,MAILING_LIST_MULTI,RDNS_DYNAMIC,URIBL_BLOCKED autolearn=ham autolearn_force=no version=3.4.2 Received: from sourceware.org (ip-8-43-85-97.sourceware.org [8.43.85.97]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (2048 bits) server-digest SHA256) (No client certificate requested) by simark.ca (Postfix) with ESMTPS id 533CB1EDEE for ; Fri, 27 Aug 2021 13:24:24 -0400 (EDT) Received: from server2.sourceware.org (localhost [IPv6:::1]) by sourceware.org (Postfix) with ESMTP id CB2A73858435 for ; Fri, 27 Aug 2021 17:24:23 +0000 (GMT) DKIM-Filter: OpenDKIM Filter v2.11.0 sourceware.org CB2A73858435 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=sourceware.org; s=default; t=1630085063; bh=4mXZBEpa7PiPv391cDoAFn2vjICBkDyyuMvMNZDhhLg=; h=Subject:To:References:Date:In-Reply-To:List-Id:List-Unsubscribe: List-Archive:List-Post:List-Help:List-Subscribe:From:Reply-To: From; b=T3GkMg+FfjTsdMwZzbaVJoTjk+dDkfYTjeohtWjof0jBt8gI9el2oenr7K7mIXvZf nFodsOzlHsVfE6IcQ8RkEzyNgkMHK09BS/cCg0+2SeYuTkN1OBlXzCwat8ODxjIoAx 4EMKFylQLGRaQiYtNa7LkAGx2YWH+BjvVyJ4WIMA= Received: from smtp.polymtl.ca (smtp.polymtl.ca [132.207.4.11]) by sourceware.org (Postfix) with ESMTPS id 77B493858D34 for ; Fri, 27 Aug 2021 17:23:55 +0000 (GMT) DMARC-Filter: OpenDMARC Filter v1.4.1 sourceware.org 77B493858D34 Received: from simark.ca (simark.ca [158.69.221.121]) (authenticated bits=0) by smtp.polymtl.ca (8.14.7/8.14.7) with ESMTP id 17RHNo7B017455 (version=TLSv1/SSLv3 cipher=ECDHE-RSA-AES256-GCM-SHA384 bits=256 verify=NOT); Fri, 27 Aug 2021 13:23:54 -0400 DKIM-Filter: OpenDKIM Filter v2.11.0 smtp.polymtl.ca 17RHNo7B017455 Received: from [10.0.0.11] (192-222-157-6.qc.cable.ebox.net [192.222.157.6]) (using TLSv1.3 with cipher TLS_AES_128_GCM_SHA256 (128/128 bits) key-exchange X25519 server-signature RSA-PSS (2048 bits)) (No client certificate requested) by simark.ca (Postfix) with ESMTPSA id EB2721EDEE; Fri, 27 Aug 2021 13:23:49 -0400 (EDT) Subject: Re: [PATCH][gdb/testsuite] Support .debug_aranges in dwarf assembly To: Tom Tromey , Simon Marchi via Gdb-patches References: <20210826115625.GA22715@delia> <87eeafovsa.fsf@tromey.com> <40b7d95e-cc02-38c7-5406-0fc83a2a1b28@polymtl.ca> <87tujaoofr.fsf@tromey.com> <5100b9c9-0a69-d392-1d45-9affe992acff@polymtl.ca> <87eeaeolu7.fsf@tromey.com> Message-ID: <7539e57d-05f5-17c4-d3df-d20c3a8d9d3a@polymtl.ca> Date: Fri, 27 Aug 2021 13:23:49 -0400 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:78.0) Gecko/20100101 Thunderbird/78.13.0 MIME-Version: 1.0 In-Reply-To: <87eeaeolu7.fsf@tromey.com> Content-Type: text/plain; charset=utf-8 Content-Language: en-US Content-Transfer-Encoding: 7bit X-Poly-FromMTA: (simark.ca [158.69.221.121]) at Fri, 27 Aug 2021 17:23:50 +0000 X-BeenThere: gdb-patches@sourceware.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: Gdb-patches mailing list List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , From: Simon Marchi via Gdb-patches Reply-To: Simon Marchi Errors-To: gdb-patches-bounces+public-inbox=simark.ca@sourceware.org Sender: "Gdb-patches" On 2021-08-27 1:10 p.m., Tom Tromey wrote: > Simon> But doing it this way makes it so that you can only invoke arange when > Simon> you are in aranges' body, isn't that useful? I guess the downside to > Simon> redefining the proc everytime is performance, but that's really not a > Simon> concern here (it runs quickly enough). > >>> To do that, it also have to delete the 'arange' proc after evaluating >>> the body. I suppose that would be alright by me. > > Simon> Really? This technique is used in proc rnglists, and that doesn't seem > Simon> to cause a problem. > > AFAIK Tcl doesn't have any kind of lexical scoping for procs. > So, after "proc arange" is evaluated, the binding stays around. > > This contradicts the what you were saying: "you can only invoke arange > when you are in aranges' body". I think that's not the case, you can > invoke arange any time after any aranges call in the current invocation > of runtest. Ah, I didn't know, I said that without actually trying it. I assumed it worked like all other languages :). > I'm not concerned about the performance, I guess. It's just > un-idiomatic to define a proc in a proc, normally this would only be > used for tricky things like changing a proc body at runtime. So when I > see this sort of thing, I start looking for the trick. There's nothing > incorrect, it's just less clear than it could be. So, defining the proc inside another is not useful then. Simon