Re: [friam] Formal modeling of systems based on E/CapTP/(Water)Ken/Cap'n Proto ideas

On Wed, Jul 8, 2015 at 1:00 PM, Tom Van Cutsem <[email protected]> wrote:

> 2015-07-07 4:47 GMT+02:00 Mark Miller <[email protected]>:
>
>> On Tue, Jul 7, 2015 at 12:10 AM, Dan Connolly <[email protected]> wrote:
>>
>>>
>>> Very interesting. I'm just starting to read it; first detail that stands
>>> out:
>>>
>>
> Me too. I like the children's playground analogy to introduce the issues
> of risk and trust :-)
>

When James first wrote this, I had misgivings but I have come to love it,
especially "and the children don't want the teachers to intervene anyway".


>
> [...]
>
>> By applying this transformation repeatedly, we move all lambda
>> expressions to be directly under a top-level def in this way. A top level
>> def whose body is a single lambda is equivalent to a class whose instance
>> variables are the f's parameters and whose behavior is the behavior of that
>> lambda expression. The top level scope of such a program consists only of
>> class names such as f, which are therefore the only variables that these
>> class definitions can use freely. Other than those, they are closed.
>>
>
> It sounds like you're describing exactly the compiler transformation known
> as "lambda lifting": <https://en.wikipedia.org/wiki/Lambda_lifting>.
>

Thanks, I think I am.


-- 
  Cheers,
  --MarkM

_______________________________________________
cap-talk mailing list
[email protected]
http://www.eros-os.org/mailman/listinfo/cap-talk