unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Stefan Monnier <monnier@IRO.UMontreal.CA>
To: Alan Mackenzie <acm@muc.de>
Cc: Glenn Morris <rgm@gnu.org>, emacs-devel@gnu.org
Subject: Re: Problem with building Emacs diagnosed.  Help please!
Date: Sun, 03 Aug 2008 14:13:50 -0400	[thread overview]
Message-ID: <jwvr696j7em.fsf-monnier+emacs@gnu.org> (raw)
In-Reply-To: <20080802101239.GA3890@muc.de> (Alan Mackenzie's message of "Sat,  2 Aug 2008 10:12:39 +0000")

> As far as I can make out (in .../lisp/emacs-lisp/autoload.el), when the
> autoload processing is done, the order in which elisp files are processed
> is random (for some value of "random").

IIRC there's some effort to try and keep it lexicographically ordered,
but IIRC it's not 100% reliable.

> So having elisp files set up so
> that they depend on the processing order is a Bad Thing.

Agreed.  And relying on the lexicographic ordering is not a good
idea either.

> However, given that we've passed the deadline for new features, I would
> like to revert that change for Emacs 23, removing `eshell-defgroup' so as
> to firm up the build process.

Sounds good to me.

> Maybe, at some stage, we could introduce a new construct, something like
>     ;;;###autoload-requires eshell.el
> , but my gut feeling is that this would be unnecessary complexity.

Agreed.

> What do people think?

Thanks for tracking it down.


        Stefan




  reply	other threads:[~2008-08-03 18:13 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-08-02 10:12 Problem with building Emacs diagnosed. Help please! Alan Mackenzie
2008-08-03 18:13 ` Stefan Monnier [this message]
2008-08-03 18:59 ` Glenn Morris
2008-08-03 22:01   ` Glenn Morris
2008-08-04 17:05   ` Alan Mackenzie
2008-08-04 18:45     ` Chong Yidong
2008-08-04 19:19       ` Alan Mackenzie
2008-08-08 22:53     ` Glenn Morris
2008-08-08 23:00       ` Lennart Borgman (gmail)
2008-08-11 19:18       ` Alan Mackenzie
2008-08-11 19:30         ` Lennart Borgman (gmail)

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=jwvr696j7em.fsf-monnier+emacs@gnu.org \
    --to=monnier@iro.umontreal.ca \
    --cc=acm@muc.de \
    --cc=emacs-devel@gnu.org \
    --cc=rgm@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).