>This is almost 20 year old memory cells trying to activate here, but I
>thought Forth was generally implemented by "compilation" into a non-standard
>pCode which was then run interpretively by a stack oriented run time engine.
That's one way of doing it, but the most traditional (and still most
popular, at least from what I see) way of doing it is to compile
straight to threaded machine code.
Note that even though threaded code is usually most commonly associated
with Forth and other "non-traditional" languages, the technique
is applicable to old-line languages as well. For example, Fortran IV
compilers on the PDP-11 could optionally compile to threaded machine code,
usually producing smaller object code as a result.
>Thus, I would have said it was a stack oriented language. But I guess it
>depends on if you're looking at the language itself or how it is normally
>executed?
To me, at least, threaded means "you call a subroutine for everything".
For instance, if you want to add two numbers, you push them onto a
(or the) stack and call the add routine. It's the extreme opositte
of "inline" code, to the point where you can think that you're working
on a "virtual" machine that doesn't have the limitations of your
"real" machine (probably why you've confused Forth with p-Code type
intermediate representations - after all, conceptually they aren't that
different!)
--
Tim Shoppa Email: shoppa(a)trailing-edge.com
Trailing Edge Technology WWW: http://www.trailing-edge.com/
7328 Bradley Blvd Voice: 301-767-5917
Bethesda, MD, USA 20817 Fax: 301-767-5927
Greetings again!
I'm in need of some printed documentation with regards to the HP2100 or
HP21MX diagnostics. While each of the diagnostics are available separately,
a large chunk of diagnostics are put on a single set of 3 paper tapes. I do
have the tapes, but not the manual that goes with it. The manual is
24396-14001. That's the one I need as this "manual" actually is a manual on
each diagnostic included in the three tapes above. Can any of the 2100 or
21MX folks check and see if they have this manual laying around?
In the event no one has 24396-14001, I would also be able to just get along
with the manuals on a few of the diagnostics. Those critical ones would be:
02100-90219 Core memory (2100/16/15/14)
24395-90001 Semiconductor memory (21MX)
02100-90221 Memory Parity Check
02100-90216 Power fail auto restart
24391-90001 General purpose register
24322-90002 Direct Memory Access (2100/21MX)
Thanks for checking!
Jay West
It is still work in progress. I have a new location for it and I am in the
process rebuilding it on this new server. It won't be much longer now.
--
Kevan
'Those who do not understand Unix are condemned to reinvent it, poorly.'
- Henry Spencer
> -----Original Message-----
> From: Aaron Christopher Finney [mailto:af-list@wfi-inc.com]
> Sent: 01 March 2000 07:07
> To: classiccmp(a)classiccmp.org
> Subject: List archives available?
>
>
>
> In searching for various things, I keep running into Kevan
> Heydon's now
> defunct archive. Has someone else made the archive available online?
>
>
>
>
Howdy;
I've long been intrigued by Symbolics LISP machines and I finally had the
opportunity to get one to poke at. (English grammar now requires me to
point out that I took advantage of that opportunity. (: )
I've been thumbing through some of the docs to get a better idea of how
things work, which effort has lead me to two questions:
1) Where am I likely to find a mouse for this beast? I haven't one and it
appears as though the environment expects to use one.
2) Can the FEP software be loaded onto a virgin disk by someone other than
Symbolics? The disk in my system may have problems, and as near as I can
tell the machines arrived new with at least a bare modicum of software on
the disk.
Inquiring minds want to know.
ok
r.
