unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: "T.V Raman" <raman@google.com>
To: Stefan Monnier <monnier@iro.umontreal.ca>
Cc: Paul Eggert <eggert@cs.ucla.edu>, Richard Stallman <rms@gnu.org>,
	emacs-devel@gnu.org
Subject: Re: Prickliness of the "invalid byte code" stuff
Date: Mon, 17 Jun 2019 17:14:52 -0700	[thread overview]
Message-ID: <p911rzrkav7.fsf@google.com> (raw)
In-Reply-To: <jwv7e9ju8lw.fsf-monnier+emacs@gnu.org> (Stefan Monnier's message of "Mon, 17 Jun 2019 18:53:57 -0400")

When it was originally introduced, I remember byte-compile-dynamic made
a significant difference when loading large modules from which one
initially used only a few functions, it enabled lazy-loading.

Would that still matter in today's emacs, or have things moved along far
enough that it wont matter?
-- 



  reply	other threads:[~2019-06-18  0:14 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 [this message]
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
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

  List information: https://www.gnu.org/software/emacs/

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

  git send-email \
    --in-reply-to=p911rzrkav7.fsf@google.com \
    --to=raman@google.com \
    --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 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).