On 06/17/2011 11:40 PM, Kevin Wright wrote:
"1842 - Ada Lovelace writes the first program. She is hampered in her
efforts by the minor inconvenience that she doesn't have any actual
computers to run her code. Enterprise architects will later relearn
her techniques in order to program in UML
On 17 June 2011 20:33, Fabrizio Giudici wrote:
> On 06/17/2011 06:49 PM, Kevin Wright wrote:
>
>>
>>
>> Agreed :)
>>
>> Phrases like "callback style" or even just "asynchronous" would probably
>> be more useful in this context, as they better reflect the intent of the
>> code.
>>
>> A few days ag
On 06/17/2011 06:49 PM, Kevin Wright wrote:
Agreed :)
Phrases like "callback style" or even just "asynchronous" would
probably be more useful in this context, as they better reflect the
intent of the code.
A few days ago I updated the draft to just call for "similarities" with
continuatio
On 17 June 2011 14:00, Alessio Stalla wrote:
> On Jun 14, 7:40 pm, Fabrizio Giudici
> wrote:
> > On 06/14/2011 02:11 PM, Kevin Wright wrote:
> >
> > > The current approach taken by Scala/C# is therefore reification of
> > > *delimited* continuations to stop you blowing the stack. This isn't
> >
On Jun 14, 7:40 pm, Fabrizio Giudici
wrote:
> On 06/14/2011 02:11 PM, Kevin Wright wrote:
>
> > The current approach taken by Scala/C# is therefore reification of
> > *delimited* continuations to stop you blowing the stack. This isn't
> > exactly an easy thing to get right, hence the fact that it
I don't know if it has a name, but it looks like a fairly normal
double-dispatch behavioral pattern which is common in UI/plugin
frameworks (i.e. JSR-296), except there it's multicast (multiple
observers/stakeholders) rather than unicast. I don't think it has
anything more to do with continuations
