[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
bug#31718: 26.1; Strange behavior of `cond'
From: |
Ikumi Keita |
Subject: |
bug#31718: 26.1; Strange behavior of `cond' |
Date: |
Wed, 06 Jun 2018 14:41:55 +0900 |
Hi Andreas, thanks for your reply.
>>>>> Andreas Schwab <schwab@suse.de> writes:
> On Jun 05 2018, Ikumi Keita <ikumi@ikumi.que.jp> wrote:
>> (defun xyz (arg)
>> "dummy"
>> ; (cond ((eq arg nil) ; OK
>> ; (cond ((eq arg 'abc) ; OK
>> ; (cond ((eq arg 'def) ; OK
>> (cond ((eq arg 'default) ; NG
> The byte-compiler uses 'default as a magic symbol, which breaks this
> case.
Does this mean that this behavior is a (new) designed feature of elisp
and not a bug?
If so, is it the respoisibility of the authors of the codes to rewrite
not to use `default' or else to make sure to set
`byte-compile-cond-use-jump-table' to nil at byte compile?
Best regards,
Ikumi Keita
- bug#31718: 26.1; Strange behavior of `cond', Ikumi Keita, 2018/06/05
- bug#31718: 26.1; Strange behavior of `cond', Andreas Schwab, 2018/06/05
- bug#31718: 26.1; Strange behavior of `cond',
Ikumi Keita <=
- bug#31718: 26.1; Strange behavior of `cond', Robert Cochran, 2018/06/06
- bug#31718: 26.1; Strange behavior of `cond', Ikumi Keita, 2018/06/06
- bug#31718: 26.1; Strange behavior of `cond', Robert Cochran, 2018/06/11
- bug#31718: 26.1; Strange behavior of `cond', Noam Postavsky, 2018/06/12
- bug#31718: 26.1; Strange behavior of `cond', Ikumi Keita, 2018/06/13
- bug#31718: 26.1; Strange behavior of `cond', Vibhav Pant, 2018/06/13
bug#31718: 26.1; Strange behavior of `cond', Paul Eggert, 2018/06/16