[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: Strange eval behaviour
From: |
Stefan Huchler |
Subject: |
Re: Strange eval behaviour |
Date: |
Fri, 18 Nov 2016 18:00:17 +0100 |
User-agent: |
Gnus/5.13 (Gnus v5.13) Emacs/25.1 (gnu/linux) |
Michael Heerdegen <michael_heerdegen@web.de> writes:
> AFAIR, you had a strange handling of variables in your code: some
> functions had used free variables that were declared nowhere. Compiling
> is a good way to reveal such problems.
Hmm I dont misunderstand you, you are talking about the params varible I
assigned a few times with setq?
I saw that only as warnings again that should not cause problems.
Or did you refer here to something different you saw? bytecompiling only
throw warnings about this params variables. And thats only warnings...
- Strange eval behaviour, Stefan Huchler, 2016/11/13
- Re: Strange eval behaviour, Stefan Monnier, 2016/11/14
- Re: Strange eval behaviour, Stefan Huchler, 2016/11/15
- Re: Strange eval behaviour, Michael Heerdegen, 2016/11/17
- Re: Strange eval behaviour, Stefan Huchler, 2016/11/18
- Re: Strange eval behaviour, Michael Heerdegen, 2016/11/18
- Re: Strange eval behaviour, Stefan Huchler, 2016/11/22
- Re: Strange eval behaviour, Michael Heerdegen, 2016/11/23
- Re: Strange eval behaviour, Stefan Huchler, 2016/11/23
- Re: Strange eval behaviour,
Stefan Huchler <=
- Re: Strange eval behaviour, Michael Heerdegen, 2016/11/18
- Re: Strange eval behaviour, Stefan Huchler, 2016/11/22
- Re: Strange eval behaviour, Stefan Huchler, 2016/11/27
- Re: Strange eval behaviour, Stefan Huchler, 2016/11/27