From: Juanma Barranquero <lekktu@gmail.com>
To: Le Wang <l26wang@gmail.com>
Cc: emacs-devel@gnu.org
Subject: Re: when to call provide, first or last?
Date: Mon, 27 Feb 2012 14:44:51 +0100 [thread overview]
Message-ID: <CAAeL0SRi+hqiv=a0pyhwiP39t9jEr9-r7kpV7tzjZh91D34e9w@mail.gmail.com> (raw)
In-Reply-To: <CAM=K+ir2Un4sTfwfZ50uwe-tB9YFJHOaMTt8-3=KheNfmToCnQ@mail.gmail.com>
On Mon, Feb 27, 2012 at 14:32, Le Wang <l26wang@gmail.com> wrote:
> So what? You have broken code. Bad things happened, and Emacs is in a bad
> state either way.
No, sorry. One package failing to load does not necessarily leave
"Emacs in a bad state", at least not in theory. That's why
ignore-errors, condition-case and (require x nil t) exist, for
example.
Your way makes a bit more difficult to detect the problem, and a bit
more likely that it will be missed and subsequent requires fail
without warning.
But, hey, it's your code, put it whenever you think it's right.
> This function announces that feature is now loaded, or being loaded, into the current Emacs session.
>
> NOTE: "or being loaded"
Right. And using your method, you can have a feature that does not
mean that the code is loaded or being loaded.
Juanma
next prev parent reply other threads:[~2012-02-27 13:44 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-02-27 12:47 when to call provide, first or last? Le Wang
2012-02-27 12:59 ` Juanma Barranquero
2012-02-27 13:09 ` Le Wang
2012-02-27 13:25 ` Juanma Barranquero
2012-02-27 13:32 ` Le Wang
2012-02-27 13:44 ` Juanma Barranquero [this message]
2012-02-27 13:57 ` Le Wang
2012-02-27 14:05 ` Drew Adams
2012-02-27 13:35 ` Stefan Monnier
2012-02-27 13:42 ` Le Wang
2012-02-27 14:25 ` Stefan Monnier
2012-02-27 15:08 ` Harald Hanche-Olsen
2012-02-27 15:46 ` Le Wang
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='CAAeL0SRi+hqiv=a0pyhwiP39t9jEr9-r7kpV7tzjZh91D34e9w@mail.gmail.com' \
--to=lekktu@gmail.com \
--cc=emacs-devel@gnu.org \
--cc=l26wang@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 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.