Byte compiling and semi-free variables

Byte compiling and semi-free variables

[Lennart Borgman]

If you order definitions top-down in your elisp source files, like this

  ;;;; Interactive defuns:

  (defun my-fun ()
    (interactive)
    (setq my-internal-var 1) )

  ;;;; Internal variables
  (defvar my-internal-var nil)

and byte-compile the files you get warnings like

  my-lib.el:118:14:Warning: reference to free variable `my-internal-var'

Is there any way to avoid that warning?

Re: Byte compiling and semi-free variables

[Juanma Barranquero]

On Sun, Dec 28, 2008 at 16:39, Lennart Borgman
<lennart.borgman@gmail.com> wrote:

> Is there any way to avoid that warning?

You could use `with-no-warnings' (which is ugly):

  (defun my-fun ()
    (interactive)
    (with-no-warnings
      (setq my-internal-var 1)))

or add a local variable:

  ;;; Local Variables:
  ;;; byte-compile-warnings: (not free-vars)
  ;;; End:

which is uglier and affects every non-declared variable in the file.

Or you could just not order the definitions top-down.

    Juanma

Re: Byte compiling and semi-free variables

[Lennart Borgman]

On Sun, Dec 28, 2008 at 4:48 PM, Juanma Barranquero <lekktu@gmail.com> wrote:
> On Sun, Dec 28, 2008 at 16:39, Lennart Borgman
> <lennart.borgman@gmail.com> wrote:
>
>> Is there any way to avoid that warning?
>
> You could use `with-no-warnings' (which is ugly):
>
>  (defun my-fun ()
>    (interactive)
>    (with-no-warnings
>      (setq my-internal-var 1)))
>
> or add a local variable:
>
>  ;;; Local Variables:
>  ;;; byte-compile-warnings: (not free-vars)
>  ;;; End:
>
> which is uglier and affects every non-declared variable in the file.
>
> Or you could just not order the definitions top-down.

Which is also rather ugly ... ;-)

Thanks.

>    Juanma
>

Byte compiling and semi-free variables

[Stephen J. Turnbull]

Lennart Borgman writes:
 > If you order definitions top-down in your elisp source files, like this
 > 
 >   ;;;; Interactive defuns:
 > 
 >   (defun my-fun ()
 >     (interactive)
 >     (setq my-internal-var 1) )
 > 
 >   ;;;; Internal variables
 >   (defvar my-internal-var nil)

But that's not top-down.  `my-internal-variable' is global, ie, it has
the same scope as `my-fun'.

If `my-internal-variable' is not intended to be global, ie, it is only
accessed in `my-fun', then you could try

(defun my-fun ()
  (interactive)
  ;; The elisp static local wannabe idiom
  (eval-when-compile (defvar my-internal-var))
  (setq my-internal-var 1))

Re: Byte compiling and semi-free variables

[Miles Bader]

"Lennart Borgman" <lennart.borgman@gmail.com> writes:
>   my-lib.el:118:14:Warning: reference to free variable `my-internal-var'
>
> Is there any way to avoid that warning?

Don't order your source files that way.  Instead, order them the usual
way, with declaration preceding use.

-Miles

-- 
Corporation, n. An ingenious device for obtaining individual profit without
individual responsibility.

Re: Byte compiling and semi-free variables

[Lennart Borgman]

On Sun, Dec 28, 2008 at 11:21 PM, Miles Bader <miles@gnu.org> wrote:
> "Lennart Borgman" <lennart.borgman@gmail.com> writes:
>>   my-lib.el:118:14:Warning: reference to free variable `my-internal-var'
>>
>> Is there any way to avoid that warning?
>
> Don't order your source files that way.  Instead, order them the usual
> way, with declaration preceding use.

Ok, thanks all for the suggestions. I give up ... ;-)