Revision as of 15:11, 22 August 2023 edit Citation bot (talk \| contribs) Bots 5,870,126 edits Alter: template type. Add: series. Removed parameters. Some additions/deletions were parameter name changes. \| Use this bot. Report bugs. \| Suggested by Headbomb \| #UCB_toolbar ← Previous edit		Revision as of 08:02, 1 September 2023 edit undo MarcGarver (talk \| contribs) Autopatrolled, Extended confirmed users, New page reviewers, Pending changes reviewers, Rollbackers 39,290 edits →History: uncited despite having quotations, and appears to be OR or POV Next edit →
Line 20: \| url= https://www.cs.tufts.edu/~nr/cs257/archive/john-reynolds/procedural-data-structures.pdf }} </ref> Reynolds discussed two forms of Data Abstraction: User-defined Types, which are now known as [[abstract data types\|Abstract Data Types]] (ADTs) (not to be confused with [[algebraic data types\|Algebraic Data Types]]), and Procedural Data Structures, which are now understood as a primitive form of Objects with only one method. He argued that they are complementary, in that User-defined Types could be extended with new behaviors, and Procedural Data Structures could be extended with new representations. He also discussed related work going back to 1967. However, Reynold's conclusions based on this early analysis turned out to be completely wrong: he wrote that adding a second method to an object "is more a tour de force than a specimen of clear programming," which completely missed the Object-Oriented paradigm and its great success. He also believed the two forms of data abstraction "are inherently distinct and complementary." Fifteen years later in 1990, [[William Cook (computer scientist)\|William Cook]]<ref name="CookOOPvsADT"> {{cite book Line 40 ⟶ 39: \| isbn= 978-3-540-46450-1}} </ref> applied Reynold's ~~seminal~~ idea in the context of Objects and Abstract Data Types, which had both grown extensively. Cook identified the matrix of representations and behaviors that are implicit in a Data Abstraction, and discussed how ADTs are based on the behavioral axis, while Objects are based on the representation axis. He provides extensive discussion of work on ADTs and Objects that are relevant to the problem. He also reviewed implementations in both styles, discussed extensibility in both directions, and also identified the importance of static typing. Most importantly, he discussed situations in which there was more flexibility than Reynolds considered, including internalization and optimization of methods.

Expression problem: Difference between revisions