[self-interest] Changing prototype chain as state machine

[ungar at mac.com]

Thanks, guys. I'll read the Ego paper. A while back I gave a keynote at OOPSLA on the role of paradox in language design.
In general, I believe that better type systems are worse--depending on the context. One loses the power of ambiguity.
However, if you are sending code to Mars, it's a good tradeoff. Anyway, I'll have to read the paper.

- David


On Sep 29, 2011, at 5:20 PM, David Goehrig wrote:

> 
> The Plaid paper lays out the same concept with stricter typing. 
> 
> I hadn't seen Ego before. 
> 
> Thanks!
> 
> -=-=- dave at nexttolast.com -=-=-
> 
> On Sep 29, 2011, at 3:47 PM, "Welch, Ronald P (US SSA)" <Ronald.P.Welch at BAESYSTEMS.com> wrote:
> 
>>  
>> Dave,
>> 
>> 
>> This reminds me of a derivation of Self called "Ego" that makes
>> steps toward adding type checking to Self. If you haven't 
>> already seen it, there is paper describing Ego here:
>> 
>> http://www.cs.cmu.edu/~aldrich/papers/
>> 
>> Ron
>> ----------=-=-=-=-=-=-=-=-========oOo========-=-=-=-=-=-=-=-=----------
>>                   mailto:Ronald.P.Welch at baesystems.com
>> ----------=-=-=-=-=-=-=-=-===================-=-=-=-=-=-=-=-=----------
>> 
>> 
>> 
>> 
>> On Sep 27, 2011, at 8:28 PM, David Goehrig wrote:
>> 
>>>  
>>> In one of the Self papers it states that assignable parent slots can be useful. And then it is largely an ignored subject from then on. 
>>> 
>>> I've been ressurrecting this idea for a web framework which models core finite state machines by exploiting assignable parent slots to only expose methods sensible for that state. 
>>> 
>>> eg. A response object has no header:Value: after the headers have already been sent, and a closed socket has no read or write: or close methods, but does have an open:
>>> 
>>> When I'm building these objects there is some default behavior that needs surpressing, specifically firing up the debugger when an unknown message send is encountered. This is heavily inspired by Randy's ARK unknown methods fall through. 
>>> 
>>> Where this has become critical is building large scale distributed applications with transparent proxies forwarding messages. Which may hit an object multiple times due to resend logic. 
>>> 
>>> Do any of the wise ones on the list know of any applications using these approaches?
>>> 
>>> If not, why?
>>> 
>>> -=-=- dave at nexttolast.com -=-=-
>>> 
>> 
>> 
> 
> 

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.selflanguage.org/pipermail/self-interest/attachments/20110929/470ebadd/attachment.html>