From: "jronald" <followait@163.com>
Subject: Re: Very basic questions.
Date: Sun, 17 Sep 2006 02:13:51 +0800 [thread overview]
Message-ID: <eehest$6v5$1@news.yaako.com> (raw)
In-Reply-To: 450bf16c$0$75039$14726298@news.sunsite.dk
Thanks for your patient help.
"Colin S. Miller" <no-spam-thank-you@csmiller.demon.co.uk>
??????:450bf16c$0$75039$14726298@news.sunsite.dk...
> jronald wrote:
>> "Colin S. Miller" <no-spam-thank-you@csmiller.demon.co.uk>
>> ??????:450bdfd3$0$75037$14726298@news.sunsite.dk...
>>>> In runtime, how does "require" know where the feature list is? There is
>>>> only machine code then.
>>>>
>>> John,
>>>
>>> (require 'feature)
>>> searches the paths listed in 'load-path',
>>> this can be added to using (add-path).
>>> It looks for a file called "feature.el" or "feature.elc".
>>>
>>>
>> Do you mean that "provide" modifies the files, both .el and .elc? I just
>> can't imagine.
> John,
>
> (require 'feature) loads the package 'feature' into
> Emacs's memory, it doesn't modify the source,
> or pre-compiled package, it just reads them.
>
"require" will find check if the feature already there first, and "provide"
will add a feature to the feature list.
How do they find the feature list? Or how do they know the memory location
where feature list is?
next prev parent reply other threads:[~2006-09-16 18:13 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-09-15 19:07 Very basic questions jronald
2006-09-16 3:40 ` John Sullivan
[not found] ` <mailman.7000.1158379340.9609.help-gnu-emacs@gnu.org>
2006-09-16 11:18 ` jronald
2006-09-16 11:28 ` Colin S. Miller
2006-09-16 11:59 ` jronald
2006-09-16 12:43 ` Colin S. Miller
2006-09-16 18:13 ` jronald [this message]
2006-09-16 18:42 ` Colin S. Miller
2006-09-18 5:42 ` Tim X
-- strict thread matches above, loose matches on Subject: below --
2006-09-15 20:22 Jay Bingham
[not found] <mailman.6992.1158351893.9609.help-gnu-emacs@gnu.org>
2006-09-15 20:48 ` jronald
2006-09-15 20:50 ` jronald
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='eehest$6v5$1@news.yaako.com' \
--to=followait@163.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.
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).