all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Stefan <monnier@iro.umontreal.ca>
Cc: emacs-devel@gnu.org, schierlm@gmx.de, rms@gnu.org
Subject: Re: `make' written in elisp
Date: Tue, 04 Jan 2005 08:59:00 -0500	[thread overview]
Message-ID: <m1ekh1qpdi.fsf-monnier+emacs@gnu.org> (raw)
In-Reply-To: <87acrp2yl3.fsf@tleepslib.sk.tsukuba.ac.jp> (Stephen J. Turnbull's message of "Tue, 04 Jan 2005 21:00:40 +0900")

Stefan> What I was talking about is things like latex-preview
Stefan> searching for some LaTeX files.  This is not done at
Stefan> startup: it is currently done at install time, and I was
Stefan> arguing about that it should be done when latex-preview is
Stefan> loaded.  Of course it may also take too much time,

> That's my point.  People are just not going to find that acceptable,
> at least they didn't with year 2000 hardware with XEmacs.

But you're comparing apples and oranges.  With XEmacs you're talking about
lots and lots of searches at every startup, whereas with AUCTeX we're talking
about several searches done only when the feature is used.

So, yes, maybe it'll be slow, but the XEmacs experience with its package
system is no evidence of it.

Stefan> So there is some amount of version-dependency checking
Stefan> now?

> No.  These are package dependencies, not version dependencies.  If a
> package uses macros from another one, it is placed in the "REQUIRES"
> make variable.  Then the libraries from those REQUIRE'd packages are
> preloaded using the -l argument to emacs.

> Theoretically these could be autogenerated, but the dependency
> trackers we've seen so far have all been buggy, and miss more
> dependencies than when doing it by hand.

The way to fix those things is to call them bugs.  The packages should have
(require 'foobar) or (eval-when-compile (require 'foobar)) so that you get
a clean error rather than a miscompile.

Of course, you don't always have much control over the upstream code, but
you can apply local patches.  The only case where (require 'foobar) can
still lead to miscompile is when old versions of `foobar' don't provide
the macro, which is why I thought you used version-dependency checking.


        Stefan

  reply	other threads:[~2005-01-04 13:59 UTC|newest]

Thread overview: 30+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-12-30 19:31 `make' written in elisp Michael Schierl
2003-12-31 22:57 ` Richard Stallman
2003-12-31 23:14   ` Michael Schierl
2004-01-01 21:10     ` Richard Stallman
2004-01-01 21:37       ` Michael Schierl
2004-01-04 23:25 ` Stefan Monnier
2005-01-02 16:06   ` Richard Stallman
2005-01-02 23:22     ` David Kastrup
2005-01-02 23:55       ` Ralf Angeli
2005-01-03  0:07         ` David Kastrup
2005-01-03  0:25           ` Ralf Angeli
2005-01-03  4:32             ` Richard Stallman
2005-01-03  8:02               ` David Kastrup
2005-01-03  9:36                 ` Eli Zaretskii
2005-01-03 16:45                   ` Stefan Monnier
2005-01-03  9:10               ` Ralf Angeli
2005-01-03 18:29                 ` Richard Stallman
2005-01-03 19:28                   ` Ralf Angeli
2005-01-03 23:10                     ` David Kastrup
2005-01-04  3:38                     ` Richard Stallman
2005-01-04 11:17                       ` Ralf Angeli
2005-01-03  0:26       ` Stefan
2005-01-03 11:05         ` Stephen J. Turnbull
2005-01-03 17:16           ` Stefan Monnier
2005-01-04 12:00             ` Stephen J. Turnbull
2005-01-04 13:59               ` Stefan [this message]
2005-01-04 14:07                 ` Miles Bader
2004-03-31 22:31 ` patch for locate-file-completion? Nic Ferrier
2004-04-01 17:34   ` Richard Stallman
     [not found] <E1CloEh-0004Sl-Hg@monty-python.gnu.org>
2005-01-04 16:10 ` `make' written in elisp Eric M. Ludlam

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=m1ekh1qpdi.fsf-monnier+emacs@gnu.org \
    --to=monnier@iro.umontreal.ca \
    --cc=emacs-devel@gnu.org \
    --cc=rms@gnu.org \
    --cc=schierlm@gmx.de \
    /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.