[e-lang] object-capabilities contrasted to objects
Mark Miller
erights at gmail.com
Wed Aug 16 18:31:44 EDT 2006
On 8/16/06, Jed at Webstart <donnelley1 at webstart.com> wrote:
> At 11:17 PM 8/15/2006, Mark S. Miller wrote:
> >...
> >One of E's main goals is to teach the ideas of object-capability
> >programming to object programmers...
>
> This goal/topic seems particularly germane to the discussion of
> whether or how "object-capabilities" differ from "objects".
>
> Is there perhaps any summary material anywhere that discusses what
> object programmers have learned in such a process?
A small number have learned. They lessons I hope more will learn include
No ambient authority
Least authority
Defensive consistency (see section 5.6 of my thesis)
Causality only by messages sent on references
Strict encapsulation
Loader isolation
http://c2.com/cgi/wiki?CapabilityOrientedProgramming
http://www.info.ucl.ac.be/~pvr/oze.pdf
Section 21.5 of my thesis on "Object-Capability Discipline"
Of all these, the one that causes the biggest change to current
software engineering practice is defensive consistency.
--
Text by me above is hereby placed in the public domain
Cheers,
--MarkM
More information about the e-lang
mailing list