* byte-compile-noruntime-functions
@ 2007-12-02 21:47 Glenn Morris
2007-12-05 1:05 ` byte-compile-noruntime-functions Glenn Morris
0 siblings, 1 reply; 4+ messages in thread
From: Glenn Morris @ 2007-12-02 21:47 UTC (permalink / raw)
To: emacs-devel
I want to apply the following patch to bytecomp.el, but I've noticed
some things about byte-compile-noruntime-functions that I don't
understand.
1) It's a global variable. It's not buffer-local, nor does it get
reset like byte-compile-unresolved-functions does (in
byte-compile-from-buffer).
2) Nothing else ever seems to remove items from it, so it just grows
and grows in any Emacs session.
Do these facts make sense?
*** bytecomp.el.~2.223.~ 2007-12-02 13:40:19.000000000 -0800
--- bytecomp.el 2007-12-02 13:41:53.000000000 -0800
***************
*** 2828,2833 ****
--- 2828,2836 ----
(list 'declared (nth 3 form))
t)) ; arglist not specified
byte-compile-function-environment)
+ ;; We are stating that it _will_ be defined at runtime.
+ (setq byte-compile-noruntime-functions
+ (delq (nth 1 form) byte-compile-noruntime-functions))
nil)
^ permalink raw reply [flat|nested] 4+ messages in thread* Re: byte-compile-noruntime-functions 2007-12-02 21:47 byte-compile-noruntime-functions Glenn Morris @ 2007-12-05 1:05 ` Glenn Morris 2007-12-05 6:05 ` byte-compile-noruntime-functions Richard Stallman 0 siblings, 1 reply; 4+ messages in thread From: Glenn Morris @ 2007-12-05 1:05 UTC (permalink / raw) To: Richard Stallman; +Cc: emacs-devel Glenn Morris wrote: > some things about byte-compile-noruntime-functions that I don't > understand. > > 1) It's a global variable. It's not buffer-local, nor does it get > reset like byte-compile-unresolved-functions does (in > byte-compile-from-buffer). > > 2) Nothing else ever seems to remove items from it, so it just grows > and grows in any Emacs session. I found some previous comments from you on this: http://lists.gnu.org/archive/html/emacs-pretest-bug/2004-01/msg00173.html From: Richard Stallman Subject: Re: `eval-when-compile' can cause incorrect byte-compiler warnings Date: Sun, 18 Jan 2004 14:16:07 -0500 "I don't think it is correct to discard the byte-compile-noruntime properties after each compilation." Do you still feel that way? ^ permalink raw reply [flat|nested] 4+ messages in thread
* Re: byte-compile-noruntime-functions 2007-12-05 1:05 ` byte-compile-noruntime-functions Glenn Morris @ 2007-12-05 6:05 ` Richard Stallman 2007-12-05 6:39 ` byte-compile-noruntime-functions Glenn Morris 0 siblings, 1 reply; 4+ messages in thread From: Richard Stallman @ 2007-12-05 6:05 UTC (permalink / raw) To: Glenn Morris; +Cc: emacs-devel I don't remember any more what byte-compile-noruntime-functions is used for. I can study it again if necessary. ^ permalink raw reply [flat|nested] 4+ messages in thread
* Re: byte-compile-noruntime-functions 2007-12-05 6:05 ` byte-compile-noruntime-functions Richard Stallman @ 2007-12-05 6:39 ` Glenn Morris 0 siblings, 0 replies; 4+ messages in thread From: Glenn Morris @ 2007-12-05 6:39 UTC (permalink / raw) To: rms; +Cc: emacs-devel Richard Stallman wrote: > I don't remember any more what byte-compile-noruntime-functions > is used for. I can study it again if necessary. I think it doesn't affect the change I wanted to make. So there's probably no pressing need to think about it. ^ permalink raw reply [flat|nested] 4+ messages in thread
end of thread, other threads:[~2007-12-05 6:39 UTC | newest] Thread overview: 4+ messages (download: mbox.gz follow: Atom feed -- links below jump to the message on this page -- 2007-12-02 21:47 byte-compile-noruntime-functions Glenn Morris 2007-12-05 1:05 ` byte-compile-noruntime-functions Glenn Morris 2007-12-05 6:05 ` byte-compile-noruntime-functions Richard Stallman 2007-12-05 6:39 ` byte-compile-noruntime-functions Glenn Morris
Code repositories for project(s) associated with this public inbox https://git.savannah.gnu.org/cgit/emacs.git This is a public inbox, see mirroring instructions for how to clone and mirror all data and code used for this inbox; as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).