[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: |
Wed, 23 Nov 2016 00:57:03 +0100 |
User-agent: |
Gnus/5.13 (Gnus v5.13) Emacs/25.1 (gnu/linux) |
Michael Heerdegen <michael_heerdegen@web.de> writes:
>> yes that was my idea about bytecompiling in general not elisp
>> specific, but if macros dont throw errors cause stuff only get
>> evaluated if its bytecompiled thats really hard to debug, or it seems
>> at least to me :)
>
> I'm not sure if I understand what you mean here...
>
If code only throughs errors when you bytecompile it but not when you
evaluate it, or run it, its hard to find the error. Aperently that
happens with such macros like function*?
- 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 <=
- Re: Strange eval behaviour, Michael Heerdegen, 2016/11/23
- Re: Strange eval behaviour, Stefan Huchler, 2016/11/23
- 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, Stefan Huchler, 2016/11/27
- Re: Strange eval behaviour, Stefan Huchler, 2016/11/27