Newsgroups: comp.lang.apl
Path: watmath!watserv1!torn.onet.on.ca!utgpu!news-server.csri.toronto.edu!rpi!usc!sol.ctr.columbia.edu!destroyer!ubc-cs!unixg.ubc.ca!kakwa.ucs.ualberta.ca!sspiff!dje
From: dje@sspiff.ampr.ab.ca (Doug Evans)
Subject: Re: Embedding J/APL/etc. into a program... (like elisp in EMACS)
Organization: Edmonton, Alberta
Date: Tue, 16 Jun 1992 18:25:55 GMT
Message-ID: <1992Jun16.182555.743@sspiff.ampr.ab.ca>
X-Newsreader: Tin 1.1 PL3
References: <1992Jun16.112411.18876@olymp.informatik.uni-bonn.de>
Lines: 22

volker@sfb256.iam.uni-bonn.de ( Volker A. Brandt) writes:
>Why not go for APL2?  For all I know, it's the only APL "dialect" that can
>be run w/o change on several platforms (PC, RS6000, 680x0).  I have to
>admit that I don't know *what* APL the ISO standard defines.

680x0? Really? (Just curious).

In it's heyday (dare I call it that), STSC's APL*PLUS/UNX was ported to
more platforms than I can remember, easily more than a dozen (all of them
Unix, of course :-).

SAX (SHARP APL/UX) has been ported to several platforms (around 6?).
Ain't available though. Sigh. :-(

Although, I should differentiate between ports and products ...
*big* difference :-)

And, while I'm throwing in useless bits of trivia ... both STSC's
APL*PLUS II/386 (sp?) and SAX are descended from STSC's APL*PLUS/UNX.
-- 
Doug Evans               | "You're just supposed to sit here?"
dje@sspiff.ampr.ab.ca    |               - Worf in a mud bath.
