From: "Jay Bingham" <b.jc-emacs@netzero.com>
Subject: RE: Very basic questions.
Date: Fri, 15 Sep 2006 20:22:49 GMT [thread overview]
Message-ID: <20060915.132318.1570.309155@webmail07.nyc.untd.com> (raw)
On Friday, September 15, 2006 at 2:07 PM jronald wrote:
> How does .el run?
> Is it an explanation language or a compilation one?
> I know little about how explanation language works.
I am not familiar with the term "explanation language" so I did a
search on the Internet for it and from the one reference that I found
to "explanation language" related to programming I do not believe
that elisp is an explanation language. Elisp can be "compiled" or it
can be run in interpreted mode.
> Take "require" for example. How does it know where the
> feature list is? Or, how does feature list make itself to be found
> by functions? Maybe the problem is what is the memory model about
> elisp.
"require" and "load" both locate modules by searching the load-path.
You can read about all of this in the elisp reference manual, which
if it is not installed on your system in the info directory it can be
found on the web.
__
J_)
C_)ingham
_____________________________________________________________________
PrivatePhone - FREE telephone number & voicemail.
A number so private, you can make it public.
http://www.privatephone.com
next reply other threads:[~2006-09-15 20:22 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-09-15 20:22 Jay Bingham [this message]
[not found] <mailman.6992.1158351893.9609.help-gnu-emacs@gnu.org>
2006-09-15 20:48 ` Very basic questions jronald
2006-09-15 20:50 ` jronald
-- strict thread matches above, loose matches on Subject: below --
2006-09-15 19:07 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
2006-09-16 18:42 ` Colin S. Miller
2006-09-18 5:42 ` Tim X
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=20060915.132318.1570.309155@webmail07.nyc.untd.com \
--to=b.jc-emacs@netzero.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).