From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!.POSTED.blaine.gmane.org!not-for-mail From: Stefan Monnier Newsgroups: gmane.emacs.devel Subject: Re: Prickliness of the "invalid byte code" stuff Date: Fri, 21 Jun 2019 10:34:46 -0400 Message-ID: References: <87tvcq9b0w.fsf@igel.home> <83v9x2svmf.fsf@gnu.org> <83fto6sphn.fsf@gnu.org> <83sgs5r20q.fsf@gnu.org> <83ef3npe85.fsf@gnu.org> Mime-Version: 1.0 Content-Type: text/plain Injection-Info: blaine.gmane.org; posting-host="blaine.gmane.org:195.159.176.226"; logging-data="37724"; mail-complaints-to="usenet@blaine.gmane.org" User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/27.0.50 (gnu/linux) Cc: emacs-devel@gnu.org, "T.V Raman" To: Eli Zaretskii Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Fri Jun 21 16:50:56 2019 Return-path: Envelope-to: ged-emacs-devel@m.gmane.org Original-Received: from lists.gnu.org ([209.51.188.17]) by blaine.gmane.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.89) (envelope-from ) id 1heKsS-0009fA-HB for ged-emacs-devel@m.gmane.org; Fri, 21 Jun 2019 16:50:56 +0200 Original-Received: from localhost ([::1]:35756 helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.86_2) (envelope-from ) id 1heKsR-0000UI-G4 for ged-emacs-devel@m.gmane.org; Fri, 21 Jun 2019 10:50:55 -0400 Original-Received: from eggs.gnu.org ([2001:470:142:3::10]:46178) by lists.gnu.org with esmtp (Exim 4.86_2) (envelope-from ) id 1heKoY-0003VW-KM for emacs-devel@gnu.org; Fri, 21 Jun 2019 10:46:55 -0400 Original-Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1heKd1-0000NR-3H for emacs-devel@gnu.org; Fri, 21 Jun 2019 10:35:00 -0400 Original-Received: from mailscanner.iro.umontreal.ca ([132.204.25.50]:15812) by eggs.gnu.org with esmtps (TLS1.0:DHE_RSA_AES_256_CBC_SHA1:32) (Exim 4.71) (envelope-from ) id 1heKcv-0000CJ-47; Fri, 21 Jun 2019 10:34:55 -0400 Original-Received: from pmg3.iro.umontreal.ca (localhost [127.0.0.1]) by pmg3.iro.umontreal.ca (Proxmox) with ESMTP id 7EC94443EAF; Fri, 21 Jun 2019 10:34:49 -0400 (EDT) Original-Received: from mail01.iro.umontreal.ca (unknown [172.31.2.1]) by pmg3.iro.umontreal.ca (Proxmox) with ESMTP id 40858443E8D; Fri, 21 Jun 2019 10:34:48 -0400 (EDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=iro.umontreal.ca; s=mail; t=1561127688; bh=oRkdLvm9j320Mv01x1ZUouIh8KKqfYhS0FM6m3afGvM=; h=From:To:Cc:Subject:References:Date:In-Reply-To:From; b=o5eJ+Wob3pQSq4H3ymOgZSALU7GxfYu3ZOfVXAKkaWpZe6sKhkm6hzQD/W1+Ow+A2 Vgnrp9f+5+grLDMhtn955EVlf6yBMvMARPb24562cyqvbFmwBX74tA0QQCqICuvYku ORtwDt9lF7yxdb8VFn8zDFoVUdRNWd50i0GZmLw024jhdsWzkhCVlBxvia3+TJXkAm o4HzIeF+EalX1o0HIoz7vV3XhNWcRA+0a2JUERjDzmdGRcuiqyq7liKIGq4m1IskpA +cqJv2MwdQ6E5SvJVHZ9c4jGFKBCNwV6qKNNkDXSCTdL4WaZWP9sZLLF/0AgqB6QCU iFmqz7QZHOyQw== Original-Received: from pastel (104-195-207-100.cpe.teksavvy.com [104.195.207.100]) by mail01.iro.umontreal.ca (Postfix) with ESMTPSA id 0714B12082B; Fri, 21 Jun 2019 10:34:47 -0400 (EDT) In-Reply-To: <83ef3npe85.fsf@gnu.org> (Eli Zaretskii's message of "Fri, 21 Jun 2019 10:52:26 +0300") X-detected-operating-system: by eggs.gnu.org: GNU/Linux 2.2.x-3.x [generic] X-Received-From: 132.204.25.50 X-BeenThere: emacs-devel@gnu.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: "Emacs development discussions." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Original-Sender: "Emacs-devel" Xref: news.gmane.org gmane.emacs.devel:238007 Archived-At: > OK, thanks. I did some more tests, and I think it's indeed OK to let > this variable do nothing. My original suggestion was just to declare it obsolete (and, as a consequence, to stop using it in our own files). So I just pushed that. We can additionally change bytecomp to simply ignore the variable, indeed, that's fine by me, but I think we can wait a bit before doing that (even until Emacs-28, if you ask me). > But I guess we still need to accept its specification in file-local > variables without any errors, at least for some time? Yes, of course. Note that when compiling the file, any unknown fie-local specifications are simply ignored, so if/when we remove the (put 'byte-compile-dynamic 'safe-local-variable 'booleanp) it will not cause an error, but it will just prompt the user whether to obey this "risky" setting instead of accepting it silently. Stefan