[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: when to call provide, first or last?
From: |
Juanma Barranquero |
Subject: |
Re: when to call provide, first or last? |
Date: |
Mon, 27 Feb 2012 14:44:51 +0100 |
On Mon, Feb 27, 2012 at 14:32, Le Wang <address@hidden> 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
- when to call provide, first or last?, Le Wang, 2012/02/27
- Re: when to call provide, first or last?, Juanma Barranquero, 2012/02/27
- Re: when to call provide, first or last?, Le Wang, 2012/02/27
- Re: when to call provide, first or last?, Juanma Barranquero, 2012/02/27
- Re: when to call provide, first or last?, Le Wang, 2012/02/27
- Re: when to call provide, first or last?,
Juanma Barranquero <=
- Re: when to call provide, first or last?, Le Wang, 2012/02/27
- RE: when to call provide, first or last?, Drew Adams, 2012/02/27
Re: when to call provide, first or last?, Stefan Monnier, 2012/02/27