From: Joe Riel <joer@san.rr.com>
To: Help GNU Emacs <help-gnu-emacs@gnu.org>
Subject: Avoiding 'reference to free variable' warnings while splitting elisp source files
Date: Sat, 23 Mar 2013 09:08:00 -0700 [thread overview]
Message-ID: <20130323090800.172d8df4@gauss> (raw)
Is there a sane way to split the source of an elisp file
while avoiding the 'reference to free variable' warnings
when byte-compiling?
The problem arises when a variable defined in one file
is used in another. How does one avoid those errors?
I have half a dozen source files that are all required
by one package. A variable may be used in several files
(generally it is used mainly in one file, which is where
it is defined (with defvar), but, must be used in another.
I've tried adding
(eval-when-compile
(require 'other-source-file))
to avoid the error; that sort of works, but not
when two files each uses a variable defined in the other.
There has to be a better way.
--
Joe Riel
next reply other threads:[~2013-03-23 16:08 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-03-23 16:08 Joe Riel [this message]
2013-03-23 16:19 ` Avoiding 'reference to free variable' warnings while splittingelisp source files Drew Adams
2013-03-23 17:30 ` Stefan Monnier
2013-03-23 18:23 ` Avoiding 'reference to free variable' warnings whilesplittingelisp " Drew Adams
2013-03-23 21:05 ` Stefan Monnier
2013-03-23 22:41 ` Avoiding 'reference to free variable' warningswhilesplittingelisp " Drew Adams
2013-03-24 9:02 ` Andreas Röhler
2013-03-24 14:34 ` Drew Adams
[not found] <mailman.22711.1364054888.855.help-gnu-emacs@gnu.org>
2013-03-23 16:11 ` Avoiding 'reference to free variable' warnings while splitting elisp " Jay Belanger
2013-03-23 16:19 ` Pascal J. Bourguignon
2013-03-23 16:51 ` Jay Belanger
2013-03-23 16:59 ` Pascal J. Bourguignon
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=20130323090800.172d8df4@gauss \
--to=joer@san.rr.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.