Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]


Groups > comp.lang.python > #43625 > unrolled thread

Re: [TYPES] The type/object distinction and possible synthesis of OOP and imperative programming languages

Started byMatthias Felleisen <matthias@ccs.neu.edu>
First post2013-04-15 09:50 -0400
Last post2013-04-15 09:50 -0400
Articles 1 — 1 participant

Back to article view | Back to comp.lang.python

This discussion starts older than the indexed window; earlier articles aren't shown. The article labeled Started by below is the oldest one visible, not the original post.


Contents

  Re: [TYPES] The type/object distinction and possible synthesis of OOP and imperative programming languages Matthias Felleisen <matthias@ccs.neu.edu> - 2013-04-15 09:50 -0400

#43625 — Re: [TYPES] The type/object distinction and possible synthesis of OOP and imperative programming languages

FromMatthias Felleisen <matthias@ccs.neu.edu>
Date2013-04-15 09:50 -0400
SubjectRe: [TYPES] The type/object distinction and possible synthesis of OOP and imperative programming languages
Message-ID<mailman.634.1366035560.3114.python-list@python.org>
On Apr 14, 2013, at 11:48 PM, Mark Janssen wrote:

>  After the 2001 "type/class unification" , it went towards Alan Kay's ideal 

Are you sure? Remember Kay's two motivations [*], which he so elegantly describes with "[the] large scale one was to find a better module scheme for complex systems involving hiding of details, and the small scale one was to find a more flexible version of assignment, and then to try to eliminate it altogether."  At least for me, this quote sends a signal to language designers that is still looking for a receiver -- Matthias

[*] http://gagne.homedns.org/~tgagne/contrib/EarlyHistoryST.html


[toc] | [standalone]


Back to top | Article view | comp.lang.python


csiph-web