|
From: | GNU bug Tracking System |
Subject: | [debbugs-tracker] bug#31734: closed (26.1; byte-compile differs with cond eq 'default) |
Date: | Sat, 16 Jun 2018 16:46:03 +0000 |
Your message dated Sat, 16 Jun 2018 09:45:47 -0700 with message-id <address@hidden> and subject line Re: bug#31718: 26.1; Strange behavior of `cond' has caused the debbugs.gnu.org bug report #31718, regarding 26.1; byte-compile differs with cond eq 'default to be marked as done. (If you believe you have received this mail in error, please contact address@hidden) -- 31718: http://debbugs.gnu.org/cgi/bugreport.cgi?bug=31718 GNU Bug Tracking System Contact address@hidden with problems
--- Begin Message ---Subject: 26.1; byte-compile differs with cond eq 'default Date: Wed, 6 Jun 2018 12:38:51 +0200 Hi.The code below shows opposite behavior byte-compiled:(setq variable 0)(cond((eq variable 'default)(message "equal"))(t(message "not equal")))Not byte-compiled output: not equalByte-compiled output: equalThank you very much.Best regards. Hector
--- End Message ---
--- Begin Message ---Subject: Re: bug#31718: 26.1; Strange behavior of `cond' Date: Sat, 16 Jun 2018 09:45:47 -0700 User-agent: Mozilla/5.0 (X11; Linux x86_64; rv:52.0) Gecko/20100101 Thunderbird/52.8.0 Eli Zaretskii wrote:If it's a regression, then let's backport, indeed.OK, done, and closing the bug report.
--- End Message ---
[Prev in Thread] | Current Thread | [Next in Thread] |