unofficial mirror of help-gnu-emacs@gnu.org
 help / color / mirror / Atom feed
From: "Ludwig, Mark" <ludwig.mark@siemens.com>
To: "tomas@tuxteam.de" <tomas@tuxteam.de>
Cc: "Pascal J. Bourguignon" <pjb@informatimago.com>,
	"help-gnu-emacs@gnu.org" <help-gnu-emacs@gnu.org>
Subject: RE: Compilation warnings of ELisp seem wrong and misleading
Date: Mon, 30 Mar 2015 19:09:30 +0000	[thread overview]
Message-ID: <BC5672F8AD4C054BAF167C9801500D1A0101AAF76B@USSLMMBX003.net.plm.eds.com> (raw)
In-Reply-To: <20150330165935.GA11134@tuxteam.de>

"tomas@tuxteam.de" wrote on Monday, March 30, 2015 12:00 PM
> 
> On Mon, Mar 30, 2015 at 03:40:21PM +0000, Ludwig, Mark wrote:
> > "Pascal J. Bourguignon" wrote:
> >
> > > "Ludwig, Mark" <ludwig.mark@siemens.com> writes:
> > >
> > > > I find my custom Elisp generates warnings that seem pretty stupid.
> > > > For example:
> > > >
> > > > emacs.el:255:10:Warning: reference to free variable `if'
> 
> Bizarre.
> 
[...]
> Here: you're in the middle of a `cond' and the clause reads "(if ...)". I'd
> expect `cond' to try to interpret "if" as a naked variable (granted, the error
> message points at another place).

Doh!  At a minimum, I guess there is a small bug in how
the warnings are reported.  Oh, well.

Thanks!

Mark


  reply	other threads:[~2015-03-30 19:09 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 ` Compilation warnings of ELisp seem wrong and misleading Pascal J. Bourguignon
2015-03-30 15:40   ` Ludwig, Mark
2015-03-30 16:59     ` tomas
2015-03-30 19:09       ` Ludwig, Mark [this message]
     [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

  List information: https://www.gnu.org/software/emacs/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=BC5672F8AD4C054BAF167C9801500D1A0101AAF76B@USSLMMBX003.net.plm.eds.com \
    --to=ludwig.mark@siemens.com \
    --cc=help-gnu-emacs@gnu.org \
    --cc=pjb@informatimago.com \
    --cc=tomas@tuxteam.de \
    /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. 
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).