Diagramming techniques for analysts and programmers
Diagramming techniques for analysts and programmers
APL function definition notation
APL '87 Proceedings of the international conference on APL: APL in transition
A proposal for blocks and exits in APL
APL '87 Proceedings of the international conference on APL: APL in transition
Managing the structured techniques: 4th edition
Managing the structured techniques: 4th edition
APL '85 Proceedings of the international conference on APL: APL and the future
Letters to the editor: go to statement considered harmful
Communications of the ACM
The time is ripe for a dyadic execute
ACM SIGAPL APL Quote Quad
ACM SIGAPL APL Quote Quad
Special control structures for APL
ACM SIGAPL APL Quote Quad
New control structures in APL?
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
Flowchart techniques for structured programming
ACM SIGPLAN Notices
A note on goto-less programming in APL using the unquote-operator
ACM SIGPLAN Notices
Porting and optimising star: a case study of suffering and surfacing
APL '92 Proceedings of the international conference on APL
Structuring functions with operators
APL '93 Proceedings of the international conference on APL
Structured APL: a proposal for block structured control flow in APL
APL '93 Proceedings of the international conference on APL
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
Is APL2 a good programming language?
APL '95 Proceedings of the international conference on Applied programming languages
New primitive ∇ for APL-style structured control
ACM SIGAPL APL Quote Quad
Hi-index | 0.00 |
It is said by non-APL-programmers that APL code is hard to read and that it is unstructured. Here we argue that APL-programmers may refute this assertion by pointing out some misunderstandings, but admittedly a final analysis will show a deeper truth in these criticisms. We will show that APL gives ample opportunity for unstructured code. Two proposals are presented to address this problem.The first rejects the developed convention for labelling and suggests the adoption of a proper style of programming enforced by a new standard of labelling. This standard will abolish unstructured code. Both negative and positive aspects of this proposal are discussed.The second proposal revives an old idea of introducing one single proper control structure into the language. This would make the current jump (→) superfluous and enforce structured code.