unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: storm@cua.dk (Kim F. Storm)
Cc: Lute Kamstra <Lute.Kamstra.lists@xs4all.nl>,
	 miles@gnu.org, snogglethorpe@gmail.com,  reiner.steib@gmx.de,
	 ding@gnus.org, emacs-devel@gnu.org
Subject: Re: require inside functions. (was: Changes in calendar/time-date.el)
Date: Fri, 08 Apr 2005 10:12:00 +0200	[thread overview]
Message-ID: <m3y8btg01b.fsf@kfs-l.imdomain.dk> (raw)
In-Reply-To: <E1DJk4c-0007Kv-Uq@fencepost.gnu.org> (Richard Stallman's message of "Thu, 07 Apr 2005 23:22:22 -0400")

Richard Stallman <rms@gnu.org> writes:

>     (require 'ft) only loads a file if 'ft is not in features.  However,
>     it unconditionally adds '(require . ft) to current-load-list.  If you
>     call a function with require a million times, this eats up 16 MB of
>     memory.
>
> This was done deliberately.  The idea is that it's useful
> to record that file foo depends on file bar, even if bar
> was already loaded before foo.

It is not _file_ foo, but _function_ foo that did (require 'bar).

Why is it useful to record that?  For what purpose?

There is no active "load" or "autoload" in progress, so the
require is done in "interactive" context.


>
> However, it isn't useful to record (require . bar) an additional time
> in current-load-list when it's already there.  So I think the right fix
> is to check with Fmember and not add it a second time.

Which means that (require 'bar) called from a function will definitely
be slowed down (depending on the length of current-load-list)!

Would it work to only add to current-load-list if loading != 0 ?

-- 
Kim F. Storm <storm@cua.dk> http://www.cua.dk




  reply	other threads:[~2005-04-08  8:12 UTC|newest]

Thread overview: 30+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <E1DGYNu-00038g-00@quimby.gnus.org>
     [not found] ` <yotly8c5jpi2.fsf@jpl.org>
2005-03-31 11:27   ` Changes in calendar/time-date.el (was: CVS update of gnus/lisp (4 files)) Reiner Steib
2005-03-31 12:20     ` Miles Bader
2005-03-31 12:58     ` Changes in calendar/time-date.el Lute Kamstra
2005-03-31 22:52       ` Miles Bader
2005-04-01  4:10       ` Richard Stallman
2005-04-04 10:25       ` Reiner Steib
2005-04-04 10:57         ` Lute Kamstra
2005-04-04 12:09           ` Reiner Steib
2005-04-04 12:52             ` Lute Kamstra
2005-04-04 17:20               ` Reiner Steib
2005-04-04 19:50                 ` Stefan Monnier
2005-04-05  7:14                 ` Kim F. Storm
2005-04-05  9:33                   ` Miles Bader
2005-04-05 10:06                     ` Kim F. Storm
2005-04-07 12:47                       ` require inside functions. (was: Changes in calendar/time-date.el) Lute Kamstra
2005-04-07 21:45                         ` Kim F. Storm
2005-04-08  0:12                           ` require inside functions Miles Bader
2005-04-08  0:45                             ` Stefan Monnier
2005-04-08  2:09                               ` Miles Bader
2005-04-08  0:21                           ` Stefan Monnier
2005-04-08  3:22                         ` require inside functions. (was: Changes in calendar/time-date.el) Richard Stallman
2005-04-08  8:12                           ` Kim F. Storm [this message]
2005-04-09  3:38                             ` require inside functions. (was: Changes in Richard Stallman
2005-04-09  9:30                               ` require inside functions Lute Kamstra
2005-04-10  1:55                                 ` Richard Stallman
2005-04-13  9:11                               ` Lute Kamstra
2005-04-15  2:44                                 ` Richard Stallman
2005-04-15  9:23                                   ` Lute Kamstra
2005-04-08  8:16                           ` David Kastrup
2005-04-05 13:54                 ` Changes in calendar/time-date.el Lute Kamstra

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=m3y8btg01b.fsf@kfs-l.imdomain.dk \
    --to=storm@cua.dk \
    --cc=Lute.Kamstra.lists@xs4all.nl \
    --cc=ding@gnus.org \
    --cc=emacs-devel@gnu.org \
    --cc=miles@gnu.org \
    --cc=reiner.steib@gmx.de \
    --cc=snogglethorpe@gmail.com \
    /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).