[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 15:20:32 +0100 |
Michael Heerdegen <michael_heerdegen@web.de> writes:
> Stefan Huchler <stefan.huchler@mail.de> writes:
>
>> 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*?
>
> What do you mean specifically?
>
> Of cause can running code produce errors.
I have no problem if running code produces a error (a error message to
be more prezise) but if it just silently fails, and just the re-evaluate
fixes it, its kind of hard to find the problem.
- 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 <=
- 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