Newsgroups: comp.lang.apl
Path: watmath!watserv1!70530.1226@compuserve.com
From: Mike Kent <70530.1226@CompuServe.COM>
Subject: APL2/PC and subdirectory-library mapping
Message-ID: <920509034337_70530.1226_CHC160-1@CompuServe.COM>
Sender: root@watserv1.waterloo.edu (Operator)
Organization: University of Waterloo
Date: Sat, 9 May 1992 03:43:37 GMT
Lines: 20

In article <92928.195059EERIG07@TECHNION.BITNET>,
<EERIG07@TECHNION.BITNET>  (noam amir) writes:

> 1 is a:, 2 is b:, 3 is c: and that's it. this is true of ibm apl2 ...

Actually, this is the _default_ behavior for apl2/pc.  One of the AP's,
either 100 or 101, allows you to map subdirectories to libraries; there
is sample code in the manual.  My system, for instance uses 1 to 4 for
drives a: to d: then sets up a half dozen other libraries as mapped to
specific subdirectories.  

Caveats:  the supported range of library numbers is 1 - 32.  You have to
          run an APL function to establish a non-default mapping (I do it
          from a fn invoked by the []LX in a WS I specify for )LOAD on
          the command line that starts APL2.  It is a nice feature of this
          design that you can change library mapppings at will, _but_
          that means you have to be careful.



