Re: Ptr and ForeignPtr Questions

Ashley Yakeley <[EMAIL PROTECTED]> wrote, > The documentation for FFI in the GHC user's guide seems to be out of date > with regard to passing Ptrs across. > > 1. My reference is > > (from

Ptr and ForeignPtr Questions

The documentation for FFI in the GHC user's guide seems to be out of date with regard to passing Ptrs across. 1. My reference is (from ) Is this the latest documentation avail

Re: Posix.runProcess

"Manuel M. T. Chakravarty" wrote: > > I am doing this kind of stuff in the `Processes' module of > > http://www.cse.unsw.edu.au/~chak/haskell/ports/ > > I have not clue whether it runs on Windows or not, but would > be interested to know if you find out. [snip] I'm afraid I won't, because I d

Re: Posix.runProcess

I am doing this kind of stuff in the `Processes' module of http://www.cse.unsw.edu.au/~chak/haskell/ports/ I have not clue whether it runs on Windows or not, but would be interested to know if you find out. Manuel -=- George Russell <[EMAIL PROTECTED]> wrote, > Volker Stolz wrote: > > > >

Re: Posix.runProcess

Volker Stolz wrote: > > In local.glasgow-haskell-users, you wrote: > > I think Posix.runProcess should give access to the eventual exit state of > > the process, if any. Two possible ways: > > > > (1) Change its result to IO (IO ExitCode), the inner action being something > > that waits for

Re: Posix.runProcess

In local.glasgow-haskell-users, you wrote: > I think Posix.runProcess should give access to the eventual exit state of > the process, if any. Two possible ways: > > (1) Change its result to IO (IO ExitCode), the inner action being something > that waits for the process to complete (without b

RE: unsafePtrCompare, anybody?

> My intuition says that none of the side-effects in my > implementation are > visible from the abstract level of the module. However, the use of > unsafePerformIO certainly modifies the behaviour of the > module. For example, > the following definitions at the beginning of a GHCi session