Comments on: Playing unsafe haskell http://therning.org/magnus/archives/249 Incoherent mumblings Tue, 18 Nov 2008 21:38:50 +0000 http://wordpress.org/?v=2.6.3 By: Magnus http://therning.org/magnus/archives/249#comment-38598 Magnus Wed, 09 May 2007 09:48:04 +0000 http://therning.org/magnus/archives/249#comment-38598 <p>Alan,</p> <p>That's a very good point. I've found that quite a few standard functions are "lazy enough", just like <code>getContents</code>.</p> <p>Thanks for the link to FRP!</p> Alan,

That’s a very good point. I’ve found that quite a few standard functions are “lazy enough”, just like getContents.

Thanks for the link to FRP!

]]> By: Alan Falloon http://therning.org/magnus/archives/249#comment-38015 Alan Falloon Mon, 07 May 2007 16:21:20 +0000 http://therning.org/magnus/archives/249#comment-38015 <p>If your event stream is actually the characters of stdin, then getContents already hides the details of the unsafeInterleaveIO for you. As in:</p> <p>getContents >>= mapM_ yourFunc . takeWhile (/= 'q')</p> <p>However, understanding the internals makes it possible to generalize this approach to one where the event stream contains richer data (such as GUI events).</p> <p>Perhaps there is more that can be learned from <a href="http://www.haskell.org/frp/" rel="nofollow">FRP</a> (functional reactive programming)</p> If your event stream is actually the characters of stdin, then getContents already hides the details of the unsafeInterleaveIO for you. As in:

getContents >>= mapM_ yourFunc . takeWhile (/= ‘q’)

However, understanding the internals makes it possible to generalize this approach to one where the event stream contains richer data (such as GUI events).

Perhaps there is more that can be learned from FRP (functional reactive programming)

]]>