From: "Pascal J. Bourguignon" <pjb@informatimago.com>
To: help-gnu-emacs@gnu.org
Subject: Re: Compilation warnings of ELisp seem wrong and misleading
Date: Mon, 30 Mar 2015 16:39:18 +0200 [thread overview]
Message-ID: <87619iy2g9.fsf@kuiper.lan.informatimago.com> (raw)
In-Reply-To: mailman.3018.1427724507.31049.help-gnu-emacs@gnu.org
"Ludwig, Mark" <ludwig.mark@siemens.com> 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
next parent reply other threads:[~2015-03-30 14:39 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <mailman.3018.1427724507.31049.help-gnu-emacs@gnu.org>
2015-03-30 14:39 ` Pascal J. Bourguignon [this message]
2015-03-30 15:40 ` Compilation warnings of ELisp seem wrong and misleading Ludwig, Mark
2015-03-30 16:59 ` tomas
2015-03-30 19:09 ` Ludwig, Mark
[not found] ` <mailman.3032.1427730039.31049.help-gnu-emacs@gnu.org>
2015-03-30 17:08 ` Pascal J. Bourguignon
2015-03-31 0:53 ` Emanuel Berg
2015-04-01 11:45 ` Ludwig, Mark
2015-04-01 12:02 ` tomas
2015-04-02 10:20 ` Philipp Stephani
[not found] ` <mailman.3123.1427888711.31049.help-gnu-emacs@gnu.org>
2015-04-01 23:08 ` Emanuel Berg
2015-03-30 13:47 Ludwig, Mark
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87619iy2g9.fsf@kuiper.lan.informatimago.com \
--to=pjb@informatimago.com \
--cc=help-gnu-emacs@gnu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.