On 02 October 2004 13:04, Tomasz Zielonka wrote:
On Fri, Oct 01, 2004 at 09:34:36PM +0100, Simon Marlow wrote:
Not currently, but I could probably implement the equivalent
(hGetArrayNonBlocking).
It is perhaps not closely related, but could we also have
Network.Socket recvFrom / sendTo
Simon Marlow writes:
I'm surprised if pointer access to memory is slower
than unsafeRead.
You were right. Now that I have made some tests, the
problem turned out to be elsewhere. Pointer access is
not to blame. ;-)
Peter
___
Glasgow-haskell-users
On Fri, Oct 01, 2004 at 09:34:36PM +0100, Simon Marlow wrote:
Not currently, but I could probably implement the equivalent
(hGetArrayNonBlocking).
It is perhaps not closely related, but could we also have Network.Socket
recvFrom / sendTo working on raw buffers?
I've attached a proposed
On Sat, Oct 02, 2004 at 02:04:19PM +0200, Tomasz Zielonka wrote:
It is perhaps not closely related, but could we also have Network.Socket
recvFrom / sendTo working on raw buffers?
I've attached a proposed implementation. It moves most of code to
recvBufFrom and sendBufTo, and changes
On 01 October 2004 08:45, Peter Simons wrote:
I am a happy user of hGetBufNonBlocking, but I have come to
realize that mutable arrays are nicer to work with than
pointers, so I have considered using hGetArray instead. I
do, however, depend on the fact that the function returns as
soon as it
Simon Marlow writes:
Not currently, but I could probably implement the
equivalent (hGetArrayNonBlocking).
If that were possible, I'd greatly appreciate it.
I'm surprised if pointer access to memory is slower than
unsafeRead. Could you post some code that we can peer at?
Not right now,
