From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!not-for-mail From: "Pascal J. Bourguignon" Newsgroups: gmane.emacs.help Subject: Re: Compilation warnings of ELisp seem wrong and misleading Date: Mon, 30 Mar 2015 16:39:18 +0200 Organization: Informatimago Message-ID: <87619iy2g9.fsf@kuiper.lan.informatimago.com> References: NNTP-Posting-Host: plane.gmane.org Mime-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 8bit X-Trace: ger.gmane.org 1427727026 2473 80.91.229.3 (30 Mar 2015 14:50:26 GMT) X-Complaints-To: usenet@ger.gmane.org NNTP-Posting-Date: Mon, 30 Mar 2015 14:50:26 +0000 (UTC) To: help-gnu-emacs@gnu.org Original-X-From: help-gnu-emacs-bounces+geh-help-gnu-emacs=m.gmane.org@gnu.org Mon Mar 30 16:50:23 2015 Return-path: Envelope-to: geh-help-gnu-emacs@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 1Ycb1C-0000Ah-8v for geh-help-gnu-emacs@m.gmane.org; Mon, 30 Mar 2015 16:50:22 +0200 Original-Received: from localhost ([::1]:34437 helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1Ycb1B-0002ws-Ig for geh-help-gnu-emacs@m.gmane.org; Mon, 30 Mar 2015 10:50:21 -0400 Original-Path: usenet.stanford.edu!fu-berlin.de!uni-berlin.de!individual.net!not-for-mail Original-Newsgroups: gnu.emacs.help Original-Lines: 53 Original-X-Trace: individual.net zn6LWOepEUO0q1A9jwCi/AXk7mLGTx+8hxsQnU68KQnytKOmfk Cancel-Lock: sha1:Mzk1ZTkyZGJhMWU3MTdjZGFmNTYxMjhkNWEzY2NhYzRhZTkwMjNkZQ== sha1:KZ4RK8nOjsHjpWXRmiElsAkZE+w= Face: iVBORw0KGgoAAAANSUhEUgAAADAAAAAwAQMAAABtzGvEAAAABlBMVEUAAAD///+l2Z/dAAAA oElEQVR4nK3OsRHCMAwF0O8YQufUNIQRGIAja9CxSA55AxZgFO4coMgYrEDDQZWPIlNAjwq9 033pbOBPtbXuB6PKNBn5gZkhGa86Z4x2wE67O+06WxGD/HCOGR0deY3f9Ijwwt7rNGNf6Oac l/GuZTF1wFGKiYYHKSFAkjIo1b6sCYS1sVmFhhhahKQssRjRT90ITWUk6vvK3RsPGs+M1RuR mV+hO/VvFAAAAABJRU5ErkJggg== X-Accept-Language: fr, es, en User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/24.3 (gnu/linux) Original-Xref: usenet.stanford.edu gnu.emacs.help:211168 X-BeenThere: help-gnu-emacs@gnu.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Users list for the GNU Emacs text editor List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: help-gnu-emacs-bounces+geh-help-gnu-emacs=m.gmane.org@gnu.org Original-Sender: help-gnu-emacs-bounces+geh-help-gnu-emacs=m.gmane.org@gnu.org Xref: news.gmane.org gmane.emacs.help:103450 Archived-At: "Ludwig, Mark" writes: > Greetings, > > I've been using an ancient Emacs (19.29) on Solaris and finally > got around to installing a current one (24.4). > > I don't normally compile my ".emacs" code, but stumbled > across a change in the compile code (compile-internal is no > longer present), and that prompted me to explicitly > byte-compile my custom Elisp code to see what other problems > that would expose, so I could take care of all of them at > the same time. > > I find my custom Elisp generates warnings that seem pretty stupid. > For example: > > emacs.el:255:10:Warning: reference to free variable `if' > emacs.el:219:8:Warning: reference to free variable `save-excursion' > emacs.el:331:41:Warning: reference to free variable `forward-char' > emacs.el:261:17:Warning: reference to free variable `insert' > emacs.el:261:17:Warning: reference to free variable `forward-sexp' > > Those are all valid functions. For example, here are lines 255-258: > > (if (not (= ans ?q)) > (progn > (goto-char found-start) > (delete-region found-start found-end))) > > This is inside a large-ish "let*" form (111 lines). > > Most of this code is duplicated on Windows, where I'm using > Emacs 24.2 (just to give some context that my Elisp > knowledge isn't all completely ancient). > > I can't see how these warnings can be correct, but there are > so many that they obscure the "meaningful" ones. Are these > sorts of warnings known flaws in the byte compiler, do I > need to compile differently, am I doing something stupid, or > what? We cannot see either, because the meaning of a sexp is determined by its surrounding form, which you didn't provide. You probably have a parenthesis problem in your let* form which makes lisp interpret some parts as being variable names instead of operators. -- __Pascal Bourguignon__ http://www.informatimago.com/ “The factory of the future will have only two employees, a man and a dog. The man will be there to feed the dog. The dog will be there to keep the man from touching the equipment.” -- Carl Bass CEO Autodesk