ACM SIGAPL APL Quote Quad
Whither (wither?) control structures?
ACM SIGAPL APL Quote Quad
Special control structures for APL
ACM SIGAPL APL Quote Quad
Of noughts and if's and matrices: some comments on APLQQ[9;2;]
ACM SIGAPL APL Quote Quad
APL functions which enhance APL branching
APL '76 Proceedings of the eighth international conference on APL
Adding a modern control structure to APL without changing the syntax
APL '76 Proceedings of the eighth international conference on APL
What lies beyond the branch arrow?
APL '75 Proceedings of seventh international conference on APL
APL '79 Proceedings of the international conference on APL: part 1
L-one-two-three (L1:..L2:..L3:) considered harmful
APL '91 Proceedings of the international conference on APL '91
APL complaints (out) of control
ACM SIGAPL APL Quote Quad
Restriction riddance: more power to parentheses
APL '94 Proceedings of the international conference on APL : the language and its applications: the language and its applications
New primitive ∇ for APL-style structured control
ACM SIGAPL APL Quote Quad
| Hi-index | 0.00 |
A recurring subject of new proposals is implementation of the control structures seen in conventional languages:---statement grouping---conditional execution, simple (IF-statement) and compound (IF-ELSE and CASE constructions)---loopsIt is however not self-evident that there is an equally great need for each of them. This paper proposes to modify the question "do we need control structures in APL" into, "Which of the generally employed control structures do we need, like, or leave?" Based on the criteria:---clarity in showing scope of effect---suppression of detail in favor of overall aim---sufficient frequency of useit will be shown that some control structures are needed and others are not.