From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!not-for-mail From: Stefan Monnier Newsgroups: gmane.emacs.devel Subject: Re: [Ann]: An Implementation of the Shen programming language in Elisp and a call for help Date: Sat, 14 May 2016 09:29:01 -0400 Message-ID: References: NNTP-Posting-Host: plane.gmane.org Mime-Version: 1.0 Content-Type: text/plain X-Trace: ger.gmane.org 1463421151 5997 80.91.229.3 (16 May 2016 17:52:31 GMT) X-Complaints-To: usenet@ger.gmane.org NNTP-Posting-Date: Mon, 16 May 2016 17:52:31 +0000 (UTC) To: emacs-devel@gnu.org Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Mon May 16 19:52:24 2016 Return-path: Envelope-to: ged-emacs-devel@m.gmane.org Original-Received: from lists.gnu.org ([208.118.235.17]) by plane.gmane.org with esmtp (Exim 4.69) (envelope-from ) id 1b2Mgp-0007Ra-OI for ged-emacs-devel@m.gmane.org; Mon, 16 May 2016 19:52:23 +0200 Original-Received: from localhost ([::1]:45620 helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1b2Mgp-0008Nj-8L for ged-emacs-devel@m.gmane.org; Mon, 16 May 2016 13:52:23 -0400 Original-Received: from eggs.gnu.org ([2001:4830:134:3::10]:37418) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1b2Mfg-0006ny-Oe for emacs-devel@gnu.org; Mon, 16 May 2016 13:51:13 -0400 Original-Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1b2Mfd-0000Qq-S9 for emacs-devel@gnu.org; Mon, 16 May 2016 13:51:12 -0400 Original-Received: from plane.gmane.org ([80.91.229.3]:36811) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1b2Mfd-0000QI-LL for emacs-devel@gnu.org; Mon, 16 May 2016 13:51:09 -0400 Original-Received: from list by plane.gmane.org with local (Exim 4.69) (envelope-from ) id 1b1ZdH-00068x-Lj for emacs-devel@gnu.org; Sat, 14 May 2016 15:29:27 +0200 Original-Received: from 45.72.245.134 ([45.72.245.134]) by main.gmane.org with esmtp (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Sat, 14 May 2016 15:29:27 +0200 Original-Received: from monnier by 45.72.245.134 with local (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Sat, 14 May 2016 15:29:27 +0200 X-Injected-Via-Gmane: http://gmane.org/ Original-Lines: 35 Original-X-Complaints-To: usenet@ger.gmane.org X-Gmane-NNTP-Posting-Host: 45.72.245.134 User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/25.1.50 (gnu/linux) Cancel-Lock: sha1:8fZ7o2jCc12Hhi9HYFqB2LEyiZk= X-detected-operating-system: by eggs.gnu.org: Genre and OS details not recognized. X-Received-From: 80.91.229.3 X-BeenThere: emacs-devel@gnu.org X-Mailman-Version: 2.1.21 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:203863 Archived-At: > 1. I can't seem to get rid of warnings when byte-compiling the generated > "shen.el" [4] even though I have the byte-compile-warnings property the top > of the file. I'm getting a lot of "unused lexical variable" warnings even > though "lexical" is in the list of warnings. I strongly dislike disabling warnings via byte-compile-warnings, so while I'm sure it can be done, I'd rather not help you with this. "Unused variable/argument" warnings can be disabled individually in the following ways (by order of preference): - Get rid of those variables/arguments. - Add an underscore in front of the variable name (that tells the byte-compiler that the variable *should not* be used). - Add an artificial use of the variable. The canonical way to do that is to add a call (ignore ) somewhere harmless. E.g. (let ((foo )) (ignore foo) ) > 2. I would like for the "shen.el" and "shen-primitives.el" [5] file to be > byte-compiled and loaded right after compilation even though they don't > have any autoloads. Currently they are only loaded with I call the function > `shen/repl` [6] which doesn't feel very responsive. Ideally they are loaded > at the time they are compiled. Compilation should happen once and for all when you install your package, so whether it's loaded right away at that point or not is not tremendously important, compared to how the package should be (auto)loaded in the other cases, when the package is already installed. IOW I don't understand what you want here. Stefan