all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Le Wang <l26wang@gmail.com>
To: Juanma Barranquero <lekktu@gmail.com>
Cc: emacs-devel@gnu.org
Subject: Re: when to call provide, first or last?
Date: Mon, 27 Feb 2012 21:32:28 +0800	[thread overview]
Message-ID: <CAM=K+ir2Un4sTfwfZ50uwe-tB9YFJHOaMTt8-3=KheNfmToCnQ@mail.gmail.com> (raw)
In-Reply-To: <CAAeL0ST3rmY0TuPW63uA2M+FzKDr0M2oWDsa3BuyxSrzm_uRww@mail.gmail.com>

[-- Attachment #1: Type: text/plain, Size: 1070 bytes --]

On Mon, Feb 27, 2012 at 9:25 PM, Juanma Barranquero <lekktu@gmail.com>wrote:

> On Mon, Feb 27, 2012 at 14:08, Le Wang <l26wang@gmail.com> wrote:
>
> >> What happens next?  You have broken code, and you're either looking at
> the
> >> backtrace or you get a ding.  How is this a problem?
>
> The problem is that you can miss the error, and also that (require
> 'my-feature) will "work" afterwards.
>

So what?  You have broken code.  Bad things happened, and Emacs is in a bad
state either way.

Are you going to fix the bug and try the require again?  If so, then you
probably know enough to know that you should use load now.  If not you're
screwed already.  Go file a bug.


>
> It's better to put it at the end and be sure that having the feature
> means that everything went OK.
>

That's not what provide means.  From the manual,
http://www.gnu.org/software/emacs/manual/html_node/elisp/Named-Features.html
:

This function announces that feature is now loaded, or being loaded, into
the current Emacs session.

NOTE: "or being loaded"



>     Juanma
>



-- 
Le

[-- Attachment #2: Type: text/html, Size: 2011 bytes --]

  reply	other threads:[~2012-02-27 13:32 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 [this message]
2012-02-27 13:44         ` Juanma Barranquero
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='CAM=K+ir2Un4sTfwfZ50uwe-tB9YFJHOaMTt8-3=KheNfmToCnQ@mail.gmail.com' \
    --to=l26wang@gmail.com \
    --cc=emacs-devel@gnu.org \
    --cc=lekktu@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.