I-Beam: Difference between revisions
Jump to navigation
Jump to search
Faun Locke (talk | contribs) (History section) |
Faun Locke (talk | contribs) mNo edit summary |
||
Line 2: | Line 2: | ||
== History == | == History == | ||
I-Beam was introduced in [[APL\360]] by implementers to execute [[wikipedia:IBM System/360|System/360]] instructions from program control. The convenience of this lead to I-Beam becoming directly available | I-Beam was introduced in [[APL\360]] by implementers to execute [[wikipedia:IBM System/360|System/360]] instructions from program control. The convenience of this lead to I-Beam becoming directly available for use by anyone.<ref>[https://dl.acm.org/doi/pdf/10.1145/585923.585925 The Design of APL]</ref> | ||
== Mnemonics == | == Mnemonics == |
Revision as of 10:06, 14 September 2022
⌶
|
I-Beam (⌶
) is a primitive monadic operator that takes a numeric code as it's operand and derives an ambivalent function which provides a range of ad-hoc operations. This range covers non-primitive functions - for example: experimental features, interpreter-level control, access to the environment, and information about APL itself.
History
I-Beam was introduced in APL\360 by implementers to execute System/360 instructions from program control. The convenience of this lead to I-Beam becoming directly available for use by anyone.[1]
Mnemonics
In general, I-Beam's numeric operand isn't intended to be easily recalled. But some are given meaningful names.
One method is to devise a name from the Roman numeral letters I, V, X, L, C, D, and M[2]
I-Beam | Numeral |
---|---|
Called Monadically | CM (900) |
Line Count | LC (50100) |