Simplicity and Compositionality in Asynchronous Programming through First Class Events (Article Version)

F# First Class Events: Simplicity and Compositionality in Imperative Reactive Programming

Don Syme's WebLog on F# and Other Research Projects — Fri, 24 Mar 2006 06:06:00 GMT

The text of this post is also available as an article, which I'll modify with latest material on this...

re: Simplicity and Compositionality in Asynchronous Programming through First Class Events (Article Version)

falcon — Sat, 11 Nov 2006 09:32:59 GMT

Is this 'wire' model described somewhere in literature?

re: Simplicity and Compositionality in Asynchronous Programming through First Class Events (Article Version)

yang — Fri, 18 May 2007 03:07:22 GMT

This is reactive programming (dataflow programming). It would be more interesting to see the more established 'arrows' abstraction for such programming models introduced into the F# library (or even the language).

re: Simplicity and Compositionality in Asynchronous Programming through First Class Events (Article Version)

dsyme — Fri, 18 May 2007 03:42:40 GMT

Hi Yang,

To some extent I agree. The mechanism described here is really designed to familiarize .NET programmers with the notion of compositionality in reactive programming. This is extremely useful (and hence interesting) to practicing .NET programmers.

From an academic persepctive arrows are more interesting and, frankly, astoundingly beautiful. We've recently begun looking at technique to integrate arrow notation into F#.

Thanks for your comment!

don

re: Simplicity and Compositionality in Asynchronous Programming through First Class Events (Article Version)

Lloyd Moore — Wed, 05 Sep 2007 22:20:44 GMT

Is it possible to attach an event to, for example, the node of a treeview, before it is added to the controls of a form?

re: Simplicity and Compositionality in Asynchronous Programming through First Class Events (Article Version)

JBorror — Fri, 23 Jan 2009 00:12:51 GMT

Any further development on arrows in F#?