L-one-two-three (L1:..L2:..L3:) considered harmful

ABSTRACT

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.

REFERENCES

• 1: F. H. D. van Batenburg, New control structures in APL?, ACM SIGAPL APL Quote Quad, v.13 n.2, December 1982 [doi>10.1145/586713.586717]
• 2: F.H.D.van Batenburg and R.Prins, "QL/APL: A leap back - or forward?" Vector vol.2, nr.2, pp.l15-117, (1985).
• 3: John Bunda, APL function definition notation, Proceedings of the international conference on APL: APL in transition, p.253-255, May 10-14, 1987, Dallas, Texas, United States
• 4: J. P. Dorocak, APL functions which enhance APL branching, Proceedings of the eighth international conference on APL, p.99-105, September 22-24, 1976, Ottawa, Canada [doi>10.1145/800114.803667]
• 5: Edsger W. Dijkstra, Letters to the editor: go to statement considered harmful, Communications of the ACM, v.11 n.3, p.147-148, March 1968 [doi>10.1145/362929.362947]
• 6: Edward V. Eusebi, Operators for program control, Proceedings of the international conference on APL: APL and the future, p.181-189, May 12-16, 1985, Seattle, Washington, United States
• 7: Jim P. Fiegenschue, A proposal for blocks and exits in APL, ACM SIGAPL APL Quote Quad, v.17 n.4, p.391-397, May 1987
• 8: Ronald Fischer, A note on goto-less programming in APL using the unquote-operator, ACM SIGPLAN Notices, v.17 n.7, July 1982 [doi>10.1145/988376.988384]
• 9: Garth H. Foster, What lies beyond the branch arrow?, Proceedings of seventh international conference on APL, p.115-122, June 11-13, 1975, Pisa, Italy [doi>10.1145/800117.803792]
• 10: W. K. Giloi , R. Hoffmann, Adding a modern control structure to APL without changing the syntax, Proceedings of the eighth international conference on APL, p.189-194, September 22-24, 1976, Ottawa, Canada [doi>10.1145/800114.803676]
• 11: K.R.Harris, "A logical control structure for APL" Congr.Proc.pp.203-210, (1973).
• 12: K.E.Iverson, "Elementary analysis" APL Press Swarthmore pp.1-288, (1976).
• 13: Franklin Kemp, Design of a structured APL, ACM SIGAPL APL Quote Quad, v.9 n.1, September 1978 [doi>10.1145/586040.586043]
• 14: J.L.F.de Kerf, "APL and structured programming; an annotated biography" APL CAM vol.8, nr.2, pp.340-363 (1986).
• 15: G.A.Langlet, "APL "RISC" Programming Style" Vector vol.6, nr.2, pp.23-24, (1989).
• 16: A.L.Lim, and G.R.Lewis, "Towards structured programs in APL" Comp.Journ. vol.18, nr.2, pp.140-143, (1974).
• 17: James Martin , Carma McClure, Diagramming techniques for analysts and programmers, Prentice-Hall, Inc., Upper Saddle River, NJ, 1985
• 18: I. Nassi , B. Shneiderman, Flowchart techniques for structured programming, ACM SIGPLAN Notices, v.8 n.8, p.12-26, August 1973 [doi>10.1145/953349.953350]
• 19: M.Osbome and F.Little, "An implementation of structured programming in APL " Comp.Joum. vol.21, nr.4, pp.311-315, (1978).
• 20: A. P. Reeves , J. Besemer, Special control structures for APL, ACM SIGAPL APL Quote Quad, v.9 n.2, December 1978 [doi>10.1145/586050.586056]
• 21: E. Yourdon, Managing the structured techniques: 4th edition, Prentice-Hall, Inc., Upper Saddle River, NJ, 1988
• 22: Zdenek V. Jizba, The time is ripe for a dyadic execute, ACM SIGAPL APL Quote Quad, v.19 n.2, p.5, Dec. 1988 [doi>10.1145/379354.379367]

INDEX TERMS

Primary Classification:
  D. Software
  D.3 PROGRAMMING LANGUAGES
      D.3.2 Language Classifications

          Nouns: APL

Additional Classification:
  D. Software
  D.2 SOFTWARE ENGINEERING
      D.2.3 Coding Tools and Techniques
          Subjects: Standards

General Terms:
Languages, Standardization