[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
bug#7145: elisp-code behaves differently after byte-compilation
From: |
Markus Sauermann |
Subject: |
bug#7145: elisp-code behaves differently after byte-compilation |
Date: |
Tue, 05 Oct 2010 19:37:03 +0200 |
User-agent: |
Mozilla/5.0 (Windows; U; Windows NT 6.0; de; rv:1.9.2.9) Gecko/20100915 Thunderbird/3.1.4 |
Hi,
Am 03.10.2010 07:12, schrieb Chong Yidong:
>
> I think we're just going to have to ask people not to do that...
>
it looks like an undocumented feature ;-)
Here is a suggestion for a patch for the documentation (trunk of emacs
Bazaar repository)
--- BEGIN ---
=== modified file 'doc/lispref/objects.texi'
--- doc/lispref/objects.texi 2010-08-19 23:23:13 +0000
+++ doc/lispref/objects.texi 2010-10-05 18:00:58 +0000
@@ -1999,6 +1999,17 @@
@result{} nil
@end group
@end example
+
+Be aware that byte-compiling a comparison of strings with @code{eq}
+might give unexpected results.
+
+@example
+@group
+(funcall (byte-compile (lambda () (let ((foo "bar"))
+ (eq foo "bar")))))
+ @result{} t
+@end group
+@end example
@end defun
@defun equal object1 object2
--- END ---
Regards
Markus