From: "Drew Adams" <drew.adams@oracle.com>
To: "'Joe Riel'" <joer@san.rr.com>,
"'Help GNU Emacs'" <help-gnu-emacs@gnu.org>
Subject: RE: Avoiding 'reference to free variable' warnings while splittingelisp source files
Date: Sat, 23 Mar 2013 09:19:30 -0700 [thread overview]
Message-ID: <D47554C1149C4238BA50628E16C79102@us.oracle.com> (raw)
In-Reply-To: <20130323090800.172d8df4@gauss>
> 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?
Use a vacuous definition: (defvar the-variable)
See (elisp) `Defining Variables':
This form defines `foo' but does not initialize it:
(defvar foo) => foo
next prev parent reply other threads:[~2013-03-23 16:19 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-03-23 16:08 Avoiding 'reference to free variable' warnings while splitting elisp source files Joe Riel
2013-03-23 16:19 ` Drew Adams [this message]
2013-03-23 17:30 ` Avoiding 'reference to free variable' warnings while splittingelisp " 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
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=D47554C1149C4238BA50628E16C79102@us.oracle.com \
--to=drew.adams@oracle.com \
--cc=help-gnu-emacs@gnu.org \
--cc=joer@san.rr.com \
/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.