On Fri, Apr 22, 2011 at 1:17 PM, Jason Dagit <dagitj@gmail.com> wrote:

It doesn't have to be a binding. If you'd prefer to provide a Haskell implementation in terms of malloc/copyBytes that sounds fine too. I wasn't sure how to best do that so a binding seemed the most straightforward.

I was looking at this after I sent the email. copyBytes and moveBytes are bindings to memcpy and memmove, not memset.

I don't see a binding to memset in Foreign. Perhaps that should be added as well.

Jason