Re: Avoiding 'reference to free variable' warnings while splitting elisp source files

[Jay Belanger]

>>> 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?
>>
>> You can put
>> (defvar variable-name)
>> in the other file.
>
> Nope.  Because then the initialization depends on the order of loading
> the files.

If there is no initial value in the defvar, then the only thing the
defvar does is quiet the compiler.