Gnus development mailing list
 help / color / mirror / Atom feed
From: Katsumi Yamaoka <yamaoka@jpl.org>
Subject: Re: Lisp error: (void-variable byte-compile-warnings)
Date: Thu, 20 Mar 2003 07:23:18 +0900	[thread overview]
Message-ID: <yotlr893yp0p.fsf@jpl.org> (raw)
In-Reply-To: <m365qfqfzl.fsf@multivac.cwru.edu>

>>>>> In <m365qfqfzl.fsf@multivac.cwru.edu>
>>>>>	prj@po.cwru.edu (Paul Jarc) wrote:

> Kevin Greiner <kgreiner@xpediantsolutions.com> wrote:

>> I believe that this has been fixed.

> Yep, I noticed that in the ChangeLog just after posting. :/

I apologize to all.  That was my fault.  It arose from the
problem that only XEmacs complains about the unbound variables
in the following form:

(let (foo bar)
  (byte-compile (lambda () (> foo bar))))
=>
While compiling toplevel forms:
  ** reference to free variable foo
  ** reference to free variable bar
-- 
Katsumi Yamaoka <yamaoka@jpl.org>



      reply	other threads:[~2003-03-19 22:23 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-03-19 16:47 Paul Jarc
2003-03-19 17:34 ` Kevin Greiner
2003-03-19 20:05   ` Paul Jarc
2003-03-19 22:23     ` Katsumi Yamaoka [this message]

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=yotlr893yp0p.fsf@jpl.org \
    --to=yamaoka@jpl.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.
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 NNTP newsgroup(s).