mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: "M. Edward Borasky" <znmeb@aracnet.com>
To: "Rick A. Hohensee" <rickh@Capaccess.org>, <linux-kernel@vger.kernel.org>
Subject: RE: Forth interpreter as kernel module
Date: Fri, 5 Apr 2002 21:10:58 -0800	[thread overview]
Message-ID: <HBEHIIBBKKNOBLMPKCBBEEOCEKAA.znmeb@aracnet.com> (raw)
In-Reply-To: <fc.00858412003a290a00858412003a290a.3a291d@Capaccess.org>

> -----Original Message-----
> From: linux-kernel-owner@vger.kernel.org
> [mailto:linux-kernel-owner@vger.kernel.org]On Behalf Of Rick A. Hohensee
> Sent: Friday, April 05, 2002 5:22 PM
> To: linux-kernel@vger.kernel.org
> Subject: Forth interpreter as kernel module

> Phil Burk is I believe still affiliated with Mills College. He'd love to
> hear about this. Mike Haas too, probably. Mike Haas wrote the kernel of
> Amiga JForth and Phil wrote all the music stuff. I added all the Linux
> syscalls to the PForth in cLIeNUX mostly out of nostalgia for JForth, a
> "...once in a paradigm thing." Jack "jax" Woehr (sp?). Phil was quite
> pleased to hear there's a PForth out there with 160 Linux syscalls as
> primitives.

Yes, Phil Burk is still doing music ... no, he's not doing it in Forth, but
in Java. Hunt up "jmsl" and "jsyn" for the details. I haven't heard much
from Jack recently; I have his book which had an ANS-ish 16-bit DOS Forth on
a floppy. At one time, I was doing some absolutely *amazing* things with
16-bit Forths on my HP100LX Palmtop PC. Still, I must confess I haven't been
to the Taygeta Scientific Forth archive in over a year.

> More to the point, Forth can be a great personalizer of unix/Linux. Sure,
> you don't want a Forth in your DNS box. (I do, but...) You do want a Forth
> in your multimedia box. Bigtime. Which is why the "forth" command in
> cLIeNUX is upforth, PForth with a unix Jones.

Well, I want a full-strength Forth in my Linux box -- I've got SwiftForth
Pro on my Windows system and I'm holding out for something of that
comprehensive nature on Linux. I have to admit I haven't played with the
gForth that I think comes with my Red Hat distro, so I don't know what it's
like. I've heard hard-core Forthers gag profusely at the mere mention of
gForth.

So, enough "old Forthers home week" on the Linux kernel mailing list, eh?

: TOOT FORTH LOVE IF HONK THEN ;
--
M. Edward (Ed) Borasky, Chief Scientist, Borasky Research
http://www.borasky-research.net  http://www.aracnet.com/~znmeb
mailto:znmeb@borasky-research.net  mailto:znmeb@aracnet.com

Q. Who invented the non-Von Neumann computer architecture?
A. John non-Von Neumann.



  reply	other threads:[~2002-04-06  5:11 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-04-06  1:22 Rick A. Hohensee
2002-04-06  5:10 ` M. Edward Borasky [this message]
2002-04-06 16:05   ` Rick A. Hohensee
  -- strict thread matches above, loose matches on Subject: below --
2002-04-08  8:53 Rick A. Hohensee
2002-04-07 10:05 forth " Rick A. Hohensee
2002-04-04 23:49 David N. Welton
2002-04-04 23:59 ` M. Edward (Ed) Borasky
2002-04-05  0:19 ` Alan Cox
2002-04-05  2:51   ` Eric W. Biederman
2002-04-05 18:16   ` benh
2002-04-07 20:50     ` Segher Boessenkool

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=HBEHIIBBKKNOBLMPKCBBEEOCEKAA.znmeb@aracnet.com \
    --to=znmeb@aracnet.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=rickh@Capaccess.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

all inboxes | Powered by JetHome®