The following message is a courtesy copy of an article
that has been posted to bit.listserv.ibm-main,alt.folklore.computers as well.

[EMAIL PROTECTED] (Shmuel  Metz , Seymour J.) writes:
> Dont forget APL Shared Variables.

re:
http://www.garlic.com/~lynn/2007k.html#67 Non-Standard Mainframe Language?
http://www.garlic.com/~lynn/2007k.html#70 Non-Standard Mainframe Language?

yes, i skipped over some of the intermediate folklore.

there was a big uproar created with the phili science center apl\360
group when the cambridge science center did cms\apl and added "system
services calls" ...  the claim was that it totally violated spirit of
apl language ...  although as i've referenced before, removing the
trivial workspace size limits of apl\360 and providing for access to
system services (like being able to do file read/writes) ... really
opened up being able to use cms\apl for real world applications.

Eventually, APL shared variables was the effective come-back from the
APL language purists on how to be able to access system services ... w/o
corrupting the purity of the APL language.

misc. past posts mentioning apl shared variable
http://www.garlic.com/~lynn/97.html#4 Mythical beasts (was IBM... mainframe)
http://www.garlic.com/~lynn/2002c.html#30 OS Workloads : Interactive etc
http://www.garlic.com/~lynn/2002n.html#66 Mainframe Spreadsheets - 1980's 
History
http://www.garlic.com/~lynn/2003n.html#8 The IBM 5100 and John Titor
http://www.garlic.com/~lynn/2004c.html#7 IBM operating systems
http://www.garlic.com/~lynn/2004n.html#37 passing of iverson
http://www.garlic.com/~lynn/2005f.html#63 Moving assembler programs above the 
line
http://www.garlic.com/~lynn/2005n.html#50 APL, J or K?
http://www.garlic.com/~lynn/2006o.html#13 The SEL 840 computer

----------------------------------------------------------------------
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to [EMAIL PROTECTED] with the message: GET IBM-MAIN INFO
Search the archives at http://bama.ua.edu/archives/ibm-main.html

Reply via email to