Beefy Boxes and Bandwidth Generously Provided by pair Networks
Perl-Sensitive Sunglasses
 
PerlMonks  

Re^2: The Basques introduced us to object orientation?

by Arunbear (Prior)
on Jan 28, 2021 at 12:24 UTC ( #11127569=note: print w/replies, xml ) Need Help??


in reply to Re: The Basques introduced us to object orientation?
in thread The Basques introduced us to object orientation?

The link to biology is probably from Alan Kay's work in OOP e.g.
I thought of objects being like biological cells and/or individual computers on a network, only able to communicate with messages
  • Comment on Re^2: The Basques introduced us to object orientation?

Replies are listed 'Best First'.
Object-Oriented Programming (Re^3: The Basques introduced us to object orientation?)
by jdporter (Canon) on Jan 28, 2021 at 17:44 UTC

    Alan Kay, who is often credited with coining the term "objected-oriented programming", was asked to provide some thoughts and history on it: (source: Stefan Ram)

    [The term "object-oriented" was first used] at Utah sometime after November 1966 when, influenced by Sketchpad, Simula, the design for the ARPAnet, the Burroughs B5000, and my background in Biology and Mathematics, I thought of an architecture for programming. It was probably in 1967 when someone asked me what I was doing, and I said: "It's object-oriented programming".

    The original conception of it had the following parts.

    • I thought of objects being like biological cells and/or individual computers on a network, only able to communicate with messages (so messaging came at the very beginning -- it took a while to see how to do messaging in a programming language efficiently enough to be useful).
    • I wanted to get rid of data. The B5000 almost did this via its almost unbelievable HW architecture. I realized that the cell/whole-computer metaphor would get rid of data, and that "<-" would be just another message token (it took me quite a while to think this out because I really thought of all these symbols as names for functions and procedures.
    • My math background made me realize that each object could have several algebras associated with it, and there could be families of these, and that these would be very very useful. The term "polymorphism" was imposed much later (I think by Peter Wegner) and it isn't quite valid, since it really comes from the nomenclature of functions, and I wanted quite a bit more than functions. I made up a term "genericity" for dealing with generic behaviors in a quasi-algebraic form.
    • I didn't like the way Simula I or Simula 67 did inheritance (though I thought Nygaard and Dahl were just tremendous thinkers and designers). So I decided to leave out inheritance as a built-in feature until I understood it better.

    My original experiments with this architecture were done using a model I adapted from van Wijngaarten's and Wirth's "Generalization of Algol" and Wirth's Euler. Both of these were rather LISP-like but with a more conventional readable syntax. I didn't understand the monster LISP idea of tangible metalanguage then, but got kind of close with ideas about extensible languages drawn from various sources, including Irons' IMP.

    The second phase of this was to finally understand LISP and then using this understanding to make much nicer and smaller and more powerful and more late-bound understructures. Dave Fisher's thesis was done in "McCarthy" style and his ideas about extensible control structures were very helpful. Another big influence at this time was Carl Hewitt's PLANNER (which has never gotten the recognition it deserves, given how well and how earlier it was able to anticipate Prolog).

    The original Smalltalk at Xerox PARC came out of the above. The subsequent Smalltalks are complained about in the end of the History chapter: they backslid towards Simula and did not replace the extension mechanisms with safer ones that were anywhere near as useful.

    OOP to me means only messaging, local retention and protection and hiding of state-process, and extreme late-binding of all things. It can be done in Smalltalk and in LISP. There are possibly other systems in which this is possible, but I'm not aware of them.

    ... [T]here were two main paths that were catalysed by Simula. The early one (just by accident) was the bio/net non-data-procedure route that I took. The other one, which came a little later as an object of study was abstract data types, and this got much more play.

    If we look at the whole history, we see that the proto-OOP stuff started with ADT, had a little fork towards what I called "objects" -- that led to Smalltalk, etc. -- but after the little fork, the CS establishment pretty much did ADT and wanted to stick with the data-procedure paradigm. Historically, it's worth looking at the USAF Burroughs 220 file system (that I described in the Smalltalk history), the early work of Doug Ross at MIT (AED and earlier) in which he advocated embedding procedure pointers in data structures, Sketchpad (which had full polymorphism -- where e.g. the same offset in its data structure meant "display" and there would be a pointer to the appropriate routine for the type of object that structure represented, etc., and the Burroughs B5000, whose program reference tables were true "big objects" and contained pointers to both "data" and "procedures" but could often do the right thing if it was trying to go after data and found a procedure pointer. And the very first problems I solved with my early Utah stuff was the "disappearing of data" using only methods and objects. At the end of the '60s (I think) Bob Balzer wrote a pretty nifty paper called "Dataless Programming", and shortly thereafter John Reynolds wrote an equally nifty paper "Gedanken" (in 1970 I think) in which he showed that using the lambda expressions the right way would allow data to be abstracted by procedures.

    The people who liked objects as non-data were smaller in number, and included myself, Carl Hewitt, Dave Reed and a few others -- pretty much all of this group were from the ARPA community and were involved in one way or another with the design of ARPAnet->Internet in which the basic unit of computation was a whole computer. But just to show how stubbornly an idea can hang on, all through the seventies and eighties, there were many people who tried to get by with "Remote Procedure Call" instead of thinking about objects and messages. Sic transit gloria mundi.

    Please note: I have touched this text up a bit, including formatting and very minor editing.

      When I think about object orientated programming I like to think about Richard Dawkins 'The Extended Phenotype'. In 'The Extended Phenotype' RD treats genetic information as being 'pure information', therefore abstracting the flow of information in a way that is independent of time. 'The Extended Phenotype' therefore forces the reader to think in an abstract way about Ecology. The same is true in OOP. The programmer is forced to abstract outside of time. The account that you give above is useful and no doubt accurate, however the development of OOP has undoubtedly been influenced by other factors that lie outside of the originators, but may never-the-less still be linked to Biology. Inevitably linguist have got involved at some point as well. I would be very surprised if no linguist has ever sort to find a natural human language that best reflects OOP.
      A reply falls below the community's threshold of quality. You may see it by logging in.

Log In?
Username:
Password:

What's my password?
Create A New User
Domain Nodelet?
Node Status?
node history
Node Type: note [id://11127569]
help
Chatterbox?
and the web crawler heard nothing...

How do I use this? | Other CB clients
Other Users?
Others chanting in the Monastery: (5)
As of 2021-10-25 20:04 GMT
Sections?
Information?
Find Nodes?
Leftovers?
    Voting Booth?
    My first memorable Perl project was:







    Results (90 votes). Check out past polls.

    Notices?