Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Path: utzoo!watmath!clyde!burl!ulysses!allegra!mit-eddie!think!harvard!seismo!rochester!bullwinkle!svax!prins
From: prins@svax.cs.cornell.edu (Jan Prins)
Newsgroups: net.lang.apl
Subject: Re: APL2 on Vax/4.2bsd and Apollo DN330 ?
Message-ID: <241@svax.cs.cornell.edu>
Date: Tue, 18-Mar-86 19:25:50 EST
Article-I.D.: svax.241
Posted: Tue Mar 18 19:25:50 1986
Date-Received: Fri, 21-Mar-86 06:21:47 EST
References: <928@umn-cs.UUCP> <259@water.UUCP>
Reply-To: prins@svax.UUCP (Jan Prins)
Organization: Cornell Univ. CS Dept, Ithaca NY
Lines: 42

I've seen a number of questions in the last few weeks about APL
implementations under Unix and for the PC.  Lee Dickey gave references 
for several products (from Dyalog, STSC and Nial Systems).  Since 
I'm familiar with the STSC products, I'm adding a few details about 
them here.

STSC sells two different APL implementations for small machines:

APL*PLUS PC
  is an assembler implementation of APL*PLUS for the IBM PC.  It comes
  with a character generator ROM that adds the APL character set to 
  the display.
  
  It implements everything available under the STSC timesharing system
  that ran under MVT.  So that's APL/360 with all the system (quad)
  variables (index origin, etc.) and the "convenience" system (quad) 
  functions (formatter, string search, function fix/representation, etc.),
  exception handling and the component file system.  
  
  It also provides access to DOS files, PC graphics and sound
  generator and, mercifully, full-screen editing.
  
  
APL*PLUS UNX
  is a larger C-based implementation of APL2 for a variety of Un*x-like
  boxes, including the PC AT, the Vaxen and Sun.
  
  It implements everything available under the STSC timesharing system
  that runs under VM.  That's VSAPL plus the system functions, exception
  handling, the component file system and most of Bob Smith's original
  nested arrays system (including the APL2 subset).
  
  This system also provides access to the native file system and has
  full-screen editing.
  
  
The workspace size in the PC implementation is about 480K, while the
UNX workspace depends on the size of the box it runs on.

Jan Prins   {ihnp4, vax135, uw-beaver}!cornell!prins
            prins@svax.cs.cornell.edu     (prins@cornell.arpa)