On Fri, Feb 27, 2009 at 12:07 AM, Achim Schneider <bars...@web.de> wrote: > "Bryan O'Sullivan" <b...@serpentine.com> wrote: > >> There's another problem with the network APIs: they mirror the BSD >> socket API too faithfully, and provide insufficient type safety. You >> can try to send on an unconnected socket, and to bind a socket that's >> already connected, both of which should be statically forbidden. The >> APIs for datagram-oriented networking ought to be distinct from the >> stream-oriented variety, I think, even if the underlying C-level >> calls end up being substantially the same. >> > Iteratees to the rescue? Ideally, we'd have a composable IO system > that's uniform across different types of IO.
I would very much like that. However, even after thinking about the problem for several problems I don't know of a generic definition that feels right. Hopefully someone smarter will come up with one. Cheers, Johan _______________________________________________ Haskell-Cafe mailing list Haskell-Cafe@haskell.org http://www.haskell.org/mailman/listinfo/haskell-cafe
