On 12 November 2005 20:07, Neil Mitchell wrote:
You can tell the difference if you try to foreign import something provided by the mingw32 libraries (eg. libmingwex.a). How does this work with WinHugs?
Not at all, there are no libming* files even on the system when WinHugs is installed.
Hmm, how does WinHugs generate FFI code? Cheers, Simon
On Wed, Nov 16, 2005 at 12:36:57PM -0000, Simon Marlow wrote:
On 12 November 2005 20:07, Neil Mitchell wrote:
You can tell the difference if you try to foreign import something provided by the mingw32 libraries (eg. libmingwex.a). How does this work with WinHugs?
Not at all, there are no libming* files even on the system when WinHugs is installed.
Hmm, how does WinHugs generate FFI code?
FFI stubs are generated and compiled by ffihugs. I'm guessing that Neil hasn't worried about hooking in ffihugs because the old winhugs predates ffihugs, and batch compilation doesn't fit very well with the interactive environment.
FFI stubs are generated and compiled by ffihugs. I'm guessing that Neil hasn't worried about hooking in ffihugs because the old winhugs predates ffihugs, and batch compilation doesn't fit very well with the interactive environment.
I don't use FFI, so i haven't really looked at it at all. Having said that, some examples such as the Win32 examples I think use FFI, and they work fine - although I have no idea what they are actually doing beneath the surface. Thanks Neil
On Thu, Nov 17, 2005 at 12:30:48AM +0000, Neil Mitchell wrote:
FFI stubs are generated and compiled by ffihugs. I'm guessing that Neil hasn't worried about hooking in ffihugs because the old winhugs predates ffihugs, and batch compilation doesn't fit very well with the interactive environment.
I don't use FFI, so i haven't really looked at it at all. Having said that, some examples such as the Win32 examples I think use FFI, and they work fine - although I have no idea what they are actually doing beneath the surface.
When (Win)Hugs loads a module that uses the FFI, it also loads a corresponding .dll file that was previously created by processing the module with ffihugs. So interactive development of modules using FFI is problematic.
participants (3)
-
Neil Mitchell -
Ross Paterson -
Simon Marlow