Subject: bug#31734: closed (Re: bug#31718: 26.1; Strange behavior of `cond')

From: [email-masked] (GNU bug Tracking System)
Date: Sat, 16 Jun 2018 16:46:03 +0000

Your bug report

#31718: 26.1; byte-compile differs with cond eq 'default

which was filed against the emacs package, has been closed.

The explanation is attached below, along with your original report.
If you require more details, please reply to [email-masked].

-- 
31718: http://debbugs.gnu.org/cgi/bugreport.cgi?bug=31718
GNU Bug Tracking System
Contact [email-masked] with problems

Subject: Re: bug#31718: 26.1; Strange behavior of `cond'
From: Paul Eggert <[email-masked]>
To: Eli Zaretskii <[email-masked]>
Cc: [email-masked], [email-masked], [email-masked], [email-masked], [email-masked], [email-masked], [email-masked], [email-masked], [email-masked], [email-masked]
Date: Sat, 16 Jun 2018 09:45:47 -0700
List-Id: <debbugs-submit.debbugs.gnu.org>

Eli Zaretskii wrote:
> If it's a regression, then let's backport, indeed.

OK, done, and closing the bug report.

Subject: 26.1; byte-compile differs with cond eq 'default
From: Héctor Enríquez Ramón <[email-masked]>
To: [email-masked]
Date: Wed, 6 Jun 2018 12:38:51 +0200
List-Id: <debbugs-submit.debbugs.gnu.org>

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 equal
Byte-compiled output: equal

Thank you very much.

Best regards. Hector