From: "Pascal J. Bourguignon" <pjb@informatimago.com>
To: help-gnu-emacs@gnu.org
Subject: Re: etymology of obarray
Date: Fri, 16 May 2014 20:41:29 +0200 [thread overview]
Message-ID: <874n0pk1ly.fsf@kuiper.lan.informatimago.com> (raw)
In-Reply-To: 87ppjdvc6o.fsf@debian.uxu
Emanuel Berg <embe8573@student.uu.se> writes:
> Joe Riel <joer@san.rr.com> writes:
>
>> Where does the word obarray originate? What is "ob"?
>
> Object, perhaps? Just a guess, but if you are
Yes, Object Array.
It already existed in MACLISP:
http://www.maclisp.info/pitmanual/symbol.html
Originally, in LISP 1.5, it was an OBLIST.
cf. page 12 of http://www.dreamsongs.com/Files/HOPL2-Uncut.pdf
And in LISP 1.5 we have those occurences of OBLIST:
grep -niH -e oblist lisp15.asm
lisp15.asm:1531: AXC OBLIST,2 POINTER TO OBJECT LIST
lisp15.asm:1534: RNT DEBUGI SKIP MARKING OBLIST IF IN A DEBUG
lisp15.asm:8871:OBLIST SYN BUCKET
lisp15.asm:8951: OBLBA,,-*-1 OBLIST OBJECT GENER068
lisp15.asm:9921: -OBLIST GPLI0823
lisp15.asm:9923: -*-1 OBLIST GPLI0825
> interested in the obarray in general I remember asking
> about it way back - because as I recall, the
> documentation was cryptic to say the least - and there
> were some very advanced replies, as I remember. So hit
> the archives, look for Emanuel Berg and "obarray" in
> the Subject header. Report back everything you learn :)
>
> As I recall, the obarray is a data structure (some kind
> of hash table) to store stuff dynamically (i.e., not
> just in memory) so that you can filter and do stuff
> with it - for example, to provide the set of operands
> possible after you invoke a command.
--
__Pascal Bourguignon__
http://www.informatimago.com/
"Le mercure monte ? C'est le moment d'acheter !"
next prev parent reply other threads:[~2014-05-16 18:41 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <mailman.1490.1400258061.1147.help-gnu-emacs@gnu.org>
2014-05-16 17:57 ` etymology of obarray Emanuel Berg
2014-05-16 18:41 ` Pascal J. Bourguignon [this message]
2014-05-16 18:25 ` B. T. Raven
2014-05-16 18:46 ` Emanuel Berg
2014-05-16 16:33 Joe Riel
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=874n0pk1ly.fsf@kuiper.lan.informatimago.com \
--to=pjb@informatimago.com \
--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.
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).