Backwards compatibility: Difference between revisions

Jump to navigation Jump to search
m
(mention ⎕ml)
(One intermediate revision by the same user not shown)
Line 29: Line 29:
In the 1970s and early 1980s it was common to create new APL implementations to run on new hardware. These implementations almost always shared the primitive set of [[APL.SV]] or another IBM APL, but often developed new [[system function]]s or other peripheral functionality to better match the host system.
In the 1970s and early 1980s it was common to create new APL implementations to run on new hardware. These implementations almost always shared the primitive set of [[APL.SV]] or another IBM APL, but often developed new [[system function]]s or other peripheral functionality to better match the host system.


Even the languages listed above may make changes to existing behavior. [[APL2]] broke from [[APL\360]] by promoting [[bracket indexing]] to higher precedence than [[stranding]], a decision that wasn't taken up by its contemporary [[Dyalog APL]], but was shared by some later dialects including [[APLX]] and [[GNU APL]]. More recently, [[Dyalog APL 13.0]] broke compatibility for the [[Power]] function while introducing [[complex number]]s, which were controversial feature for that and other reasons. Some dialects include a [[compatibility setting]] as a [[system variable]].
Even the languages listed above may make changes to existing behavior. [[APL2]] broke from [[APL\360]] by promoting [[bracket indexing]] to higher [[precedence]] than [[stranding]], a decision that wasn't taken up by its contemporary [[Dyalog APL]], but was shared by some later dialects including [[APLX]] and [[GNU APL]]. More recently, [[Dyalog APL 13.0]] broke compatibility for the [[Power]] function while introducing [[complex number]]s, which were controversial feature for that and other reasons. Some dialects include a [[compatibility setting]] as a [[system variable]].


Notable APL dialects or offshoots that discard backwards compatibility with APL in significant ways include:
Notable APL dialects or offshoots that discard backwards compatibility with APL in significant ways include:
Line 47: Line 47:


* [[wikipedia:Backward compatibility|Backward compatibility]]
* [[wikipedia:Backward compatibility|Backward compatibility]]
* [https://github.com/abrudz/KINGDOM KINGDOM] (an example of the minimal changes necessary for an [[APL\360]] game to modern [[Dyalog APL]] and serving it as a web app)
* [https://github.com/abrudz/KINGDOM KINGDOM] (an example of the minimal changes necessary for an [[APL\360]] game to run on modern [[Dyalog APL]] and being served as a web app)
{{Template:APL development}}[[Category:APL history]][[Category:Culture]]
{{Template:APL development}}[[Category:APL history]][[Category:Culture]]

Navigation menu