[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Docstring prevents constant from being fully byte-compiled
From: |
Joe Riel |
Subject: |
Docstring prevents constant from being fully byte-compiled |
Date: |
Sun, 10 Mar 2013 23:26:47 -0700 |
Byte-compile the following (Emacs 23.3.1)
(defconst A "A")
(defconst B "B")
(defconst AB1
(concat constA constB))
(defconst AB2
(concat constA constB)
"docstring")
I get
(byte-code "\303B\304\305!\210\306B\307\310!\210\311B\312 \nP!\207"
[current-load-list constA constB A (lambda (#1=#:defconst-tmp-var) (defconst A
#1#)) "A" B (lambda (#2=#:defconst-tmp-var) (defconst B #2#)) "B" AB1 (lambda
(#3=#:defconst-tmp-var) (defconst AB1 #3#))] 3)
#@11 docstring
(defconst AB2 (concat constA constB) (#$ . 800))
Note that AB2 retains the original (non-byte-compiled) definition, while AB1
does not.
Is that actually the case? Is AB2 byte-compiled, or not?
Why does the presence of the docstring make a difference?
--
Joe Riel
[Prev in Thread] |
Current Thread |
[Next in Thread] |
- Docstring prevents constant from being fully byte-compiled,
Joe Riel <=