all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: "Óscar Fuentes" <ofv@wanadoo.es>
To: help-gnu-emacs@gnu.org
Subject: Re: Requiring elisp that comes with Emacs
Date: Tue, 31 Jan 2017 21:03:45 +0100	[thread overview]
Message-ID: <878tpr9eu6.fsf@wanadoo.es> (raw)
In-Reply-To: CANc-5UxbTorFnx+qWGm3UORx67KnXCi32Kyn6Lh6Zn_6k9=b1w@mail.gmail.com

Skip Montanaro <skip.montanaro@gmail.com> writes:

> On Tue, Jan 31, 2017 at 8:39 AM, Óscar Fuentes <ofv@wanadoo.es> wrote:
>
>> Type
>>
>> C-h f require [ENTER]
>>
>> A *Help* buffer will popup with the docstring for `require'. There it is
>> explained that the file for the require-d package is inferred from the
>> package name.
>>
>
> Thanks. When I said "this is all speculation", I meant how it works under
> the covers (how it compares semantically to Python's import statement or
> C++'s namespace statement), not how it locates a file to load. I realize
> that require uses the argument symbol name as the basename of the source
> file.

I don't know about Python, but Elisp `require' is totally unrelated to
C++'s namespace statement. Semantically, it is loosely related to the
#include preprocessor directive, although not quite the same.

IMHO it is wrong to learn a language thinking on supposedly similar
conceps on other languages. It just creates confusion.




  reply	other threads:[~2017-01-31 20:03 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-01-30 16:52 Requiring elisp that comes with Emacs Narendra Joshi
2017-01-30 18:50 ` Skip Montanaro
2017-01-31 13:46   ` Narendra Joshi
2017-01-31 14:39     ` Óscar Fuentes
2017-01-31 18:06       ` Skip Montanaro
2017-01-31 20:03         ` Óscar Fuentes [this message]
2017-01-31 14:50     ` Skip Montanaro
2017-01-31 20:01       ` Narendra Joshi
2017-01-31 20:40         ` Skip Montanaro
2017-02-01 10:07           ` hector
2017-02-01 15:10           ` Narendra Joshi
2017-02-01 15:53     ` Eric Abrahamsen

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=878tpr9eu6.fsf@wanadoo.es \
    --to=ofv@wanadoo.es \
    --cc=help-gnu-emacs@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 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.