From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!not-for-mail From: "Juanma Barranquero" Newsgroups: gmane.emacs.devel Subject: Re: frame-local variables weirdness Date: Mon, 22 Oct 2007 18:17:01 +0200 Message-ID: References: NNTP-Posting-Host: lo.gmane.org Mime-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit X-Trace: ger.gmane.org 1193069849 25090 80.91.229.12 (22 Oct 2007 16:17:29 GMT) X-Complaints-To: usenet@ger.gmane.org NNTP-Posting-Date: Mon, 22 Oct 2007 16:17:29 +0000 (UTC) Cc: rms@gnu.org, emacs-devel@gnu.org To: "Stefan Monnier" Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Mon Oct 22 18:17:29 2007 Return-path: Envelope-to: ged-emacs-devel@m.gmane.org Original-Received: from lists.gnu.org ([199.232.76.165]) by lo.gmane.org with esmtp (Exim 4.50) id 1Ijzxw-0004do-Fn for ged-emacs-devel@m.gmane.org; Mon, 22 Oct 2007 18:17:20 +0200 Original-Received: from localhost ([127.0.0.1] helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1Ijzxo-0002n6-EQ for ged-emacs-devel@m.gmane.org; Mon, 22 Oct 2007 12:17:12 -0400 Original-Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1Ijzxj-0002h9-2W for emacs-devel@gnu.org; Mon, 22 Oct 2007 12:17:07 -0400 Original-Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1Ijzxg-0002cs-9m for emacs-devel@gnu.org; Mon, 22 Oct 2007 12:17:06 -0400 Original-Received: from [199.232.76.173] (helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1Ijzxg-0002cG-4p for emacs-devel@gnu.org; Mon, 22 Oct 2007 12:17:04 -0400 Original-Received: from wa-out-1112.google.com ([209.85.146.179]) by monty-python.gnu.org with esmtp (Exim 4.60) (envelope-from ) id 1Ijzxf-0003zn-G7 for emacs-devel@gnu.org; Mon, 22 Oct 2007 12:17:03 -0400 Original-Received: by wa-out-1112.google.com with SMTP id k34so1431049wah for ; Mon, 22 Oct 2007 09:17:02 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=beta; h=domainkey-signature:received:received:message-id:date:from:to:subject:cc:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references; bh=pItFoYuR6bMoTcNoz865OVKzXSeoSmDQrWqa7WApBLQ=; b=g8ZtXbORUmJe3o8x9oNqZTX4OT2p2Cu7AO2qZxVaJLnO4R7ROz4LUU/XrXMV7ykDQvF4NEsAl4ildgTlZl7aRe/eIglLF46AFOKd5423cMXDzhzyDAXziWpopQ47hWxGwGTRyBCljnosoXAD25nSqzpVNLxYW1qM3GMTjz47mBs= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=beta; h=received:message-id:date:from:to:subject:cc:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references; b=Ha6WqiDyZvDpGBDpG7uaVsv/eHf54jaM9YiVHK+/QLWX05eL8EDyyPJ3BtT+ouaxovLWG/TUZ430O+/+dwvzwYoSS6eQymPdNEAL8jynLrr6nDxxKmzHxppmJ2vgKDC36fsEwzKTQ1dLxr9FaJ8TqNhPkTkyYGrym/txXusHJMk= Original-Received: by 10.114.174.2 with SMTP id w2mr5678998wae.1193069821967; Mon, 22 Oct 2007 09:17:01 -0700 (PDT) Original-Received: by 10.115.72.13 with HTTP; Mon, 22 Oct 2007 09:17:01 -0700 (PDT) In-Reply-To: Content-Disposition: inline X-detected-kernel: by monty-python.gnu.org: Linux 2.6 (newer, 2) X-BeenThere: emacs-devel@gnu.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: "Emacs development discussions." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Original-Sender: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Errors-To: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Xref: news.gmane.org gmane.emacs.devel:81469 Archived-At: On 10/22/07, Stefan Monnier wrote: > You mean it showed up in real use? Well, I wasn't looking for bugs or deliberately constructing convoluted test cases, I just happened to stumble upon it, but I don't remember anymore whether that was in a piece of code or just while trying to understand the implications of frame-local variables. The example I sent is a convoluted test case, though, designed to highlight the problem. Anyway, what I meant is that if we allow variables that can be both automatically-buffer local and frame-local, and we consider as a feature that a piece of code "works right" without knowing whether some variable has been made frame-local or not behind it's back, and add to it that what triggers the bug is a *read* of the variable's value at the wrong time... I'd say is a real bug of the "I won't encounter it in a million years, but the moment I do, I'll have an interesting time debugging it" variety. YMMV. All in all, I think in this case we're in violent agreement. Juanma