From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!.POSTED.blaine.gmane.org!not-for-mail From: Eli Zaretskii Newsgroups: gmane.emacs.devel Subject: Re: Prickliness of the "invalid byte code" stuff Date: Fri, 21 Jun 2019 18:04:49 +0300 Message-ID: <834l4jou7i.fsf@gnu.org> References: <87tvcq9b0w.fsf@igel.home> <83v9x2svmf.fsf@gnu.org> <83fto6sphn.fsf@gnu.org> <83sgs5r20q.fsf@gnu.org> <83ef3npe85.fsf@gnu.org> Injection-Info: blaine.gmane.org; posting-host="blaine.gmane.org:195.159.176.226"; logging-data="130333"; mail-complaints-to="usenet@blaine.gmane.org" Cc: emacs-devel@gnu.org, raman@google.com To: Stefan Monnier Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Fri Jun 21 17:10:13 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 1heLB6-000Xn4-PZ for ged-emacs-devel@m.gmane.org; Fri, 21 Jun 2019 17:10:12 +0200 Original-Received: from localhost ([::1]:35928 helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.86_2) (envelope-from ) id 1heLB5-0005i2-MX for ged-emacs-devel@m.gmane.org; Fri, 21 Jun 2019 11:10:11 -0400 Original-Received: from eggs.gnu.org ([2001:470:142:3::10]:51604) by lists.gnu.org with esmtp (Exim 4.86_2) (envelope-from ) id 1heL6L-0002cU-RJ for emacs-devel@gnu.org; Fri, 21 Jun 2019 11:05:18 -0400 Original-Received: from fencepost.gnu.org ([2001:470:142:3::e]:42519) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1heL6L-0005Ci-Hk; Fri, 21 Jun 2019 11:05:17 -0400 Original-Received: from [176.228.60.248] (port=3877 helo=home-c4e4a596f7) by fencepost.gnu.org with esmtpsa (TLS1.2:RSA_AES_256_CBC_SHA1:256) (Exim 4.82) (envelope-from ) id 1heL6H-0001bX-I0; Fri, 21 Jun 2019 11:05:16 -0400 In-reply-to: (message from Stefan Monnier on Fri, 21 Jun 2019 10:34:46 -0400) X-detected-operating-system: by eggs.gnu.org: GNU/Linux 2.2.x-3.x [generic] 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:238008 Archived-At: > From: Stefan Monnier > Cc: "T.V Raman" , emacs-devel@gnu.org > Date: Fri, 21 Jun 2019 10:34:46 -0400 > > > 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). Fine with 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. The prompts are annoying, so I think we should do something to avoid them in this specific case.