|
|||||||||||||||||||||||||||||||
|
|||||||||||||||||||||||||||||||
 ABSTRACT
The importance of Object-Oriented techniques is perhaps one of the most significant changes in programming over the last decade or more; in 1991, a team of three (Jacob Brickman, Michael J. Kent, and the author) began looking into what would be required to extend APL interpreters to provide native support for OO. At this writing, we have a great deal of agreement about overall architecture, some significant issues to resolve, an overall consensus that it is time to share these ideas, and we have also come a long way in learning what is required of APL interpreter developers. This effort has driven each of us into topics we might not have explored otherwise, and this knowledge has been used to good effect elsewhere. The purpose of this paper is not so much in providing exhaustive enumeration of the definitions we have agreed upon, but to introduce our architecture to interested parties, show that APL can be extended with OO in reasonable ways, and stimulate serious discussion of this topic among system developers and other APL implementers. REFERENCES
Note: OCR errors may be found in this Reference List extracted from the full text article. ACM has opted to expose the complete List rather than only correct and linked references.
INDEX TERMS
Primary Classification:
Additional Classification:
Peer to Peer - Readers of this Article have also read:
The ACM Portal is published by the Association for Computing Machinery. Copyright © 2009 ACM, Inc.
Terms of Usage Privacy Policy Code of Ethics Contact Us Useful downloads:  Adobe Acrobat
 QuickTime
 Windows Media Player
 Real Player
|
|||||||||||||||||||||||||||||||
Pdf
D.3