all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: Stefan Monnier <monnier@iro.umontreal.ca>
Cc: eggert@cs.ucla.edu, rms@gnu.org, emacs-devel@gnu.org
Subject: Re: Prickliness of the "invalid byte code" stuff
Date: Wed, 19 Jun 2019 19:08:37 +0300	[thread overview]
Message-ID: <83sgs5r20q.fsf@gnu.org> (raw)
In-Reply-To: <jwv36k67l4p.fsf-monnier+emacs@gnu.org> (message from Stefan Monnier on Tue, 18 Jun 2019 15:48:30 -0400)

> From: Stefan Monnier <monnier@iro.umontreal.ca>
> Cc: eggert@cs.ucla.edu,  rms@gnu.org,  emacs-devel@gnu.org
> Date: Tue, 18 Jun 2019 15:48:30 -0400
> 
> >> A `grep byte-compile-dynamic: **/*.el` seems to indicate it's currently
> >> used in 12 files bundled with Emacs.
> > Any idea why those 12 use it?
> 
> I think in the 20th century, the performance difference could be
> measured (at least in benchmarks, tho maybe also in actual use), but
> I seriously doubt it makes a noticeable difference on machines of this
> century (not sure if it's because of changes in hardware such as
> available RAM or CPU speed, or because the growth of the rest of
> Emacs dwarfs those effects, or what).

I understand, but I was curious why these 12 files do use the
variable, while all the rest don't.  IOW, what is (or was) so special
about these files?

I think I'd like to wait with the decision until we hear the
emacsspeak results.  I expect that the effect on the memory will be
minor, even in a package _all_ of whose files use this variable.  If
that is indeed so, I think we can disable the variable.



  parent reply	other threads:[~2019-06-19 16:08 UTC|newest]

Thread overview: 40+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-06-15 12:36 Prickliness of the "invalid byte code" stuff Lars Ingebrigtsen
2019-06-15 14:30 ` Andreas Schwab
2019-06-16  2:40   ` Richard Stallman
2019-06-16 12:41     ` Lars Ingebrigtsen
2019-06-16 13:27       ` Stefan Monnier
2019-06-16 17:47     ` T.V Raman
2019-06-16 22:01       ` Stefan Monnier
2019-06-17  2:39         ` T.V Raman
2019-06-17 13:32           ` Stefan Monnier
2019-06-17 16:04             ` Richard Stallman
2019-06-17 18:10               ` Stefan Monnier
2019-06-17 22:52                 ` Paul Eggert
2019-06-17 22:53                   ` Stefan Monnier
2019-06-18  0:14                     ` T.V Raman
2019-06-18 12:14                       ` Stefan Monnier
2019-06-18 13:51                         ` T.V Raman
2019-06-18 14:15                           ` T.V Raman
2019-06-18 16:31                     ` Eli Zaretskii
2019-06-18 18:11                       ` Stefan Monnier
2019-06-18 18:23                         ` T.V Raman
2019-06-18 18:52                           ` Eli Zaretskii
2019-06-18 19:54                             ` T.V Raman
2019-06-19  2:36                               ` Eli Zaretskii
2019-06-19 13:54                                 ` T.V Raman
2019-06-19 15:36                                   ` Eli Zaretskii
2019-06-18 18:44                         ` Eli Zaretskii
2019-06-18 19:48                           ` Stefan Monnier
2019-06-18 19:52                             ` Stefan Monnier
2019-06-19 16:08                             ` Eli Zaretskii [this message]
2019-06-19 16:25                               ` Stefan Monnier
2019-06-19 17:04                                 ` Eli Zaretskii
2019-06-19 19:02                               ` Stefan Monnier
2019-06-19 21:35                                 ` T.V Raman
2019-06-21  7:52                                   ` Eli Zaretskii
2019-06-21 14:10                                     ` T.V Raman
2019-06-21 14:15                                       ` Eli Zaretskii
2019-06-21 14:34                                     ` Stefan Monnier
2019-06-21 15:04                                       ` Eli Zaretskii
2019-06-18  3:09                 ` Richard Stallman
2019-06-17 16:01           ` Richard Stallman

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=83sgs5r20q.fsf@gnu.org \
    --to=eliz@gnu.org \
    --cc=eggert@cs.ucla.edu \
    --cc=emacs-devel@gnu.org \
    --cc=monnier@iro.umontreal.ca \
    --cc=rms@gnu.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
Code repositories for project(s) associated with this external index

	https://git.savannah.gnu.org/cgit/emacs.git
	https://git.savannah.gnu.org/cgit/emacs/org-mode.git

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.