View source for GHC/Using the FFI

[[Category:GHC|FFI]]
==Introduction==

The examples below show how to call C++ functions in a Microsoft Windows Visual Studio DLL from Haskell, and Haskell functions from the C++ DLL. This illustrates that it is possible to link Haskell built with GHC to code produced by a different C compiler (GHC uses GCC), and also illustrates some workarounds to the specific problems encountered when building a standalone library (in this case a Windows DLL) that is to be called from Haskell.

The examples are also relevant for the simpler case where you just want to statically link against C that is compiled with GCC.  However, there are other pages that cover other aspects of Haskell's FFI:

* [[FFI_Introduction|An introduction to the Haskell FFI]]
* [[FFI_complete_examples|Some complete examples of using the Haskell FFI]]
* [[Using_Haskell_in_an_Xcode_Cocoa_project|Building a Haskell library to be used in a Mac OS X Cocoa project]]
* [[FFICookBook|The FFI cookbook]]
* [http://book.realworldhaskell.org/read/interfacing-with-c-the-ffi.html Interfacing with C: the FFI], Chapter 17 of [http://book.realworldhaskell.org Real World Haskell] by Bryan O'Sullivan, Don Stewart, and John Goerzen.  It will guide you through the writing of the bindings to the PCRE library. Very useful and nicely conceived.
* [http://www.haskell.org/onlinereport/haskell2010/haskellch8.html Foreign Function Interface] in the Haskell 2010 Language Report
* [http://research.microsoft.com/~simonpj/papers/marktoberdorf/ Tackling the Awkward Squad] A paper by Simon Peyton-Jones which includes discussion of the issues surrounding the design of the FFI

== Importing C functions that turn out to be CPP macros ==

Some C functions are actually defined by a CPP header file to be a C macro.  Suppose you <tt>foreign import</tt> such a "function", thus:
<haskell>
foreign import foo :: Int -> IO Int
</haskell> 
Then you'll get the right thing if you compile using <tt>-fvia-C</tt>, provided you cause the right header files to be included.  But the native code generator knows nothing of CPP macros, so it will generate a call to a non-existent C function "foo".
In effect, the FFI is defined to interface to the C ABI rather than the C API; it doesn't take account of CPP magic.

To work around this you typically need to write yourself a C wrapper function (in C), thus:
<haskell>
int foo_wrap(int x) { return foo(x); }
</haskell>
This C wrapper lives in a .c file and gets compiled by the C compiler.  Then use the Haskell FFI to foreign-import that, rather than calling the C function directly:
<haskell>
foreign import "foo_wrap" foo :: Int -> IO Int
</haskell> 
We have lots of examples scattered about the libraries already.

==Callbacks into Haskell from foreign code==

Suppose we have foreign code that takes a function as an argument:

<tt>callerback.h</tt>:

 #ifndef CALLERBACK_H
 #define CALLERBACK_H
 typedef double (d2d)(double);
 double twice(d2d f, double x);
 #endif

<tt>callerback.c</tt>:

 #include "callerback.h"
 double twice(d2d f, double x) {
   return f(f(x));
 }

We can provide a Haskell function as an argument like this:

<tt>CallBacker.hs</tt>:
 {-# LANGUAGE ForeignFunctionInterface #-}
 module Main(main) where
 
 -- we need CDouble for C's double type; Haskell's Double may be different
 import Foreign.C.Types(CDouble(..))
 -- we need function pointer type and free function
 import Foreign.Ptr(FunPtr, freeHaskellFunPtr)
 
 -- a "wrapper" import gives a factory for converting a Haskell function to a foreign function pointer
 foreign import ccall "wrapper"
   wrap :: (CDouble -> CDouble) -> IO (FunPtr (CDouble -> CDouble))
 
 -- import the foreign function as normal
 foreign import ccall "callerback.h twice"
   twice :: FunPtr (CDouble -> CDouble) -> CDouble -> IO CDouble
 
 -- here's the function to use as a callback
 square :: CDouble -> CDouble
 square x = x * x
 
 main :: IO ()
 main = do
   squareW <- wrap square     -- make function pointer from the function
   let x = 4
   y <- twice squareW x       -- use the foreign function with our callback
   z <- twice squareW y
   print y                    -- see that it worked
   print z
   freeHaskellFunPtr squareW  -- clean up after ourselves

This can be compiled and linked with this <tt>Makefile</tt>:

 CallBacker: CallBacker.hs callerback.c callerback.h
 	ghc -O2 -Wall -o CallBacker CallBacker.hs callerback.c

A very simple example, but hopefully enough to see what is going on.

Important: don't put "unsafe" on callerback, since it calls back to haskell via the wrapped function! If you compile with -threaded, your program might simply hang on the callback with no hint as to what went wrong (compiling without -threaded, however, might give you a hint).

==Including the FFI header==
The typedefs needed by foreign C functions are in <code>HsFFI.h</code>. However, this file includes various other files, which in turn include other files, and makes use of various definitions which would need to be defined somewhere etc, and doesn't compile under Visual C++ (for example).

All in all, the simplest solution is to just make your own header with just the typedefs that are actually needed, and put this in your project directory, for example as <code>FFI.h</code>:
 #ifndef FFI_H
 #define FFI_H
 
 typedef unsigned int HsChar;  // on 32 bit machine
 typedef int HsInt;
 typedef unsigned int HsWord;
 
 // Ensure that we use C linkage for HsFunPtr 
 #ifdef __cplusplus
 extern "C"{
 #endif
 
 typedef void (*HsFunPtr)(void);
 
 #ifdef __cplusplus
 }
 #endif
 
 typedef void *HsPtr;
 typedef void *HsForeignPtr;
 typedef void *HsStablePtr;
 
 #define HS_BOOL_FALSE 0
 #define HS_BOOL_TRUE 1
 #endif // FFI_H

Note that there is no point including prototypes for the functions <code>hs_free_fun_ptr</code> etc, because there is no way to link a standalone C library (such as a DLL) to them. However this is not a problem because your Haskell code can explicitly pass the Haskell versions of these functions (wrapped in a <code>FunPtr</code>) to your C library if you need them.



==Calling Haskell from C==
As mentioned above, when building a standalone C library, we can't link our C code to the C functions like <code>hs_free_fun_ptr</code>. However we can solve this problem by passing a <code>FunPtr</code> to the Haskell function <code>freeHaskellFunPtr</code> to our library at runtime.

In the following code, we provide a Haskell function to try to initialize our C library (eg the DLL), run some Haskell code which would set up some call backs, enter some kind of message loop (eg for a Windows app), then deinitialize the C library:
 module Duma
      ( run
      , module Duma.Font
      ) where
 
 import Foreign.Ptr
 import Foreign.ForeignPtr
 import Control.Exception (bracket)
 import Duma.Font
 import Control.Monad (when)
 
 foreign import ccall duma_begin :: FunPtr (FunPtr a -> IO ()) -> IO Bool
 foreign import ccall duma_end :: IO ()
 foreign import ccall duma_run :: IO () -- implements a Windows message loop
 
 foreign import ccall "wrapper" mkFreeFunPtr :: (FunPtr a -> IO ()) -> IO (FunPtr (FunPtr a -> IO ()))
 
 run :: IO a -> IO ()
 run f = bracket
           (mkFreeFunPtr freeHaskellFunPtr
           )
           (\freeFunPtrFn -> do
              duma_end
              freeHaskellFunPtr freeFunPtrFn
           )
           (\freeFunPtrFn -> do
              initialized <- duma_begin freeFunPtrFn
              when (initialized)
                (f >> duma_run)
           )

An example of C code would be:

  typedef void (*FunPtrFn)(HsFunPtr fn);
  FunPtrFn freeFunPtrFn = NULL;
  
  __declspec(dllexport) HsBool duma_begin(HsFunPtr freeFunPtrFnRaw){
     freeFunPtrFn = reinterpret_cast&lt;FunPtrFn&gt;(freeFunPtrFnRaw);
     return HS_BOOL_TRUE;
  }

Then within some C function which needs to release a FunPtr, you can just write:
  (*freeFunPtrFn)(the_fun_ptr_to_free);

Note that it is not safe to use the <code>freeFunPtrFn</code> to free itself, because some implementations of <code>FunPtr</code> store exit code (as well as entry code) in the <code>FunPtr</code> thus a <code>FunPtr</code> needs to be thought of as a function ''holder'' rather than just a function pointer (this is why the definition of <code>run</code> above frees the pointer from the Haskell side once we've already deinitialized the C library).

A scavenger pattern ([http://www.haskell.org//pipermail/glasgow-haskell-users/2006-March/009907.html]) can be used to avoid the danger of a <code>FunPtr</code> being freed while the function it points to (actually ''holds'') is still being executed.

Note that a direct pointer to the <code>hs_free_fun_ptr</code> function can be obtained this way:

  foreign import ccall "&" hs_free_fun_ptr :: FunPtr (FunPtr a -> IO ())

==Improving efficiency==
There are two types of foreign call:
# those where the foreign function may call back into Haskell (includes anything which makes use of the Haskell runtime) before the original foreign call returns
# those where the function will always return without first calling back into Haskell.
In the first case, a significant amount of book-keeping is required to ensure that Haskell is ready to accept "incomming" calls from the foreign function before it returns, whereas in the second, since there is no danger of a call back into the Haskell runtime, nothing special needs to be done except to marshal the arguments and result as usual. Therefore the second type of call can be made a lot faster.
To specify which type of call to use with a given foreign function, the FFI provides the keywords <code>safe</code> and <code>unsafe</code>. The default is <code>safe</code> (calls which might call back into Haskell before returning), so we only need to annotate those functions which we know will not call back into Haskell eg in our example above:

  foreign import ccall unsafe duma_createFont :: CString -> IO (Ptr RawFont)
  foreign import ccall unsafe
     "&duma_releaseFont"   -- note the ampersand
     duma_releaseFont :: FunPtr (Ptr RawFont -> IO ())

Note that <code>duma_run</code> still needs to be <code>safe</code> because it will execute Haskell IO actions in response to Windows messages (the actual code for doing this is not included in the example), and <code>duma_end</code> also needs to be <code>safe</code> because it will make use of the Haskell function <code>freeHaskellFunPtr</code> (or <code>hs_free_fun_ptr</code>) to free any callbacks that were registered before returning. The annotation you choose for <code>duma_begin</code> would depend on whether or not you need to call back into the Haskell runtime during initialization of your DLL.

Caution! If you are not responsible for the source of the foreign function you should not mark the import as <code>unsafe</code> unless you are absolutely certain it doesn't (and won't ever) call back into Haskell... If in doubt, consider posting a question to the Haskell Cafe or GHC User's mailing list.

==GHC and DLLs==

===Example of aquiring and using a foreign resource===
Suppose you are writing a DLL to provide a nice windowing environment for Haskell, and you want to let Haskell obtain a text font. Suppose a font is implemented by the C++ class Font, defined by:
 // Duma_Font.h
 namespace Duma {
    class Font {
    public:
       Font(const char *name) : refcount(0){/* details omitted! */}
       ~Font(){}
       
       void AddRef() const{++refcount;}
       void Release() const{if (!--refcount) delete this;}
       
    private:
       mutable unsigned int refcount;
    };
 } // Duma

Continuing with our example DLL called <code>Duma</code>, we now edit <code>Duma.h</code> to add the following prototypes:
  // Duma.h
  #ifndef __DUMA_H  // be careful to use #ifndef (!)
  #define __DUMA_H
  
  // This header needs to be understood by VC++ and GCC
  // When included in the source for building the DLL,
  // __DUMA_DLL_EXPORT must be defined
  
  #ifdef __DUMA_DLL_EXPORT
  #define DUMA_API __declspec(dllexport)
  #else
  #define DUMA_API
  #endif
  
  #ifdef __cplusplus
    extern "C" {
  #endif
  
  DUMA_API HsPtr duma_createFont(const char *name);
  DUMA_API void duma_releaseFont(HsPtr fontRaw);
  
  #ifdef __cplusplus
    }
  #endif
  #endif // __DUMA_H

We need to tell GHC about these, so we edit <code>Duma.def</code>:
  LIBRARY Duma
  EXPORTS
    duma_createFont
    duma_releaseFont

Then we implement them in <code>Duma.cpp</code>:
  // Duma.cpp
  #include "stdafx.h"
  #include "FFI.h"
  
  // Note we have to define __DUMA_DLL_EXPORT and also
  // make sure FFI.h is included before we inlcude Duma.h
  #define __DUMA_DLL_EXPORT
  #include "Duma.h"
  #include "Duma_Font.h"
  
  BOOL APIENTRY DllMain( HANDLE hModule, 
                         DWORD  ul_reason_for_call, 
                         LPVOID lpReserved
                        ){
    // Note this is a *very* dangerous function so do nothing at all in here
    // It is not known which DLLs are currently loaded
    // If you need to do initialization/deinitialization, you should do
    // this explicitly by exporting init/deinit functions to be called from
    // Haskell
    return TRUE;
  }
  
  using namespace Duma;
  
  #ifdef __cplusplus
    extern "C" {
  #endif
  
  DUMA_API HsPtr duma_createFont(const char *name){
    Font *fontRaw = new Font(name);
    fontRaw->AddRef();
    return fontRaw;
  }
  
  DUMA_API void duma_releaseFont(HsPtr fontRaw){
    reinterpret_cast&lt;Font *&gt;(fontRaw)->Release();
  }
  
  #ifdef __cplusplus
    }
  #endif

The header <code>Duma.h</code> is used both within our DLL and externally, by GCC, to verify that the foreign function prototypes match those expected by the FFI. When used within the DLL, we make <code>DUMA_API</code> expand to the relevant linkage declaration for Visual C++ by defining <code>__DUMA_DLL_EXPORT</code>. Since (we hope) this symbol will not be defined when GCC sees the header, GCC will see a view of the header suitable for it.

Also in regards to the header, we have made our own local FFI typedefs to avoid the problems of trying to get <code>HsFFI.h</code> and all that it includes, to compile. However GCC will see the real <code>HsFFI.h</code> so when we include <code>Duma.h</code> in our DLL, we have to remember to include <code>FFI.h</code> before it. Of course we could have used some other symbol and another <code>#ifdef</code> in <code>Duma.h</code> to cause <code>FFI.h</code> to be included when needed but since <code>Duma.h</code> is only used in one place in the DLL ie by <code>Duma.cpp</code> there does not seem much point in going to this extra trouble.

The next thing is to create a Haskell module which will allow us to treat fonts as values which are automatically released when they are no longer needed, so for this we edit a module eg <code>Duma.Font</code> by creating a directory called <code>Duma</code> in the same directory as your C++ files, then creating a file <code>Font.hs</code> in this directory:
  module Duma.Font
     ( createFont
     , Font
     ) where
  
  import Foreign.C.String
  import Foreign.Ptr
  import Foreign.ForeignPtr
  import Control.Exception (block)
  
  data RawFont -- corresponds to the C++ Font
  newtype Font = Font (ForeignPtr RawFont) deriving (Eq, Ord)
  
  foreign import ccall duma_createFont :: CString -> IO (Ptr RawFont)
  foreign import ccall
     "&duma_releaseFont"   -- note the ampersand
     duma_releaseFont :: FunPtr (Ptr RawFont -> IO ())
  
  createFont :: String -> IO Font
  createFont name = block $ do
     f <- (withCString name $ \cname -> duma_createFont cname) >>=
                 newForeignPtr duma_releaseFont
     return $ Font f

There are several points to note about this code:
# We are using three types of pointers:
#; <code>Ptr</code> : Corresponds to a plain C pointer
#; <code>FunPtr</code> : Points to a Haskell or (in this case) C function, and encapsulates marshalling details necessary both before entry and after leaving the function. ''For this reason a <code>FunPtr</code> must never be destroyed while the function it points to is still being executed''
#; <code>ForeignPtr</code> : Associates a plain C pointer with a finalizer function which will be invoked when the ForeignPtr value is garbage collected
# It is important to realise that the type declaration of a foreign import shows the type of the Haskell value, not the type of the corresponding C entity that the Haskell value is bound to. When the specification of the C entity in quotes is omitted, the FFI binds a Haskell value of type <code>A -> B</code> (or <code>IO B</code>) to a C function that takes a single argument of type <code>A</code> and returns a value of type <code>B</code>. If the Haskell value just has type <code>B</code> (or <code>IO B</code>), the FFI expects to find a C ''function'' that takes ''no arguments'' and returns a value of type <code>B</code>. However in the case of <code>duma_releaseFont</code>, the Haskell value is a function pointer, and we want this to ''point to'' the C function <code>duma_releaseFont</code>, thus we need to explicitly specify the C entity being bound and put an ampersand before the C name, to indicate that we are binding to the ''address'' of the C function not the C function itself. If we omitted the ampersand, the FFI would think that the C entity to use was a function taking no arguments that returned the function pointer rather than actually being the function pointer itself. It is worth taking the time to achieve clarity about the difference between a function and a pointer to a function, especially since this distinction is blurred in C by the implicit "casting" of a function name (which is considered to ''be'' the function itself, and which is not a first class value in C) to the address of a function. Luckily, if you are building with an optimized build, or use the <code>-fviaC</code> option, GCC will give an error message if you forget the ampersand, but beware: GHC native compilation will silently succeed and your app will mysteriously crash.
# <code>block</code> is used to make the creation of the font atomic with respect to asynchronous exceptions
# <code>withCString</code> marshalls a Haskell <code>String</code> to a null terminated C string, and <code>newForeignPtr</code> takes the <code>Ptr RawFont</code> returned by <code>duma_createFont</code> and returns a <code>ForeignPtr RawFont</code> so that <code>duma_releaseFont</code> will be called on the underlying <code>Ptr RawFont</code> when the <code>ForeignPtr RawFont</code> value is no longer needed. Finally we wrap the <code>ForeignPtr RawFont</code> in a newtype to hide all this from the end user.

===Debugging Haskell DLLs===

Some folks tend to use print, putStrLn, hPutStrLn and friends to emit debug messages to stdout or stderr. This works fine, if you are developing console application, but if you are writing DLL then you can't be sure that it will be embeded in a process with console interface. The problem is that when the process is with graphical interface, then it doesn't have associated stdin, stdout and stderr at all. Any attempt to use putStrLn for example will raise an exception and the process will terminate. The solution is to use Debug.Trace.trace or Debug.Trace.putTraceMsg instead. When they are called from a process with console interface then the messages are redirected to stderr. When the process is with graphical interface then the debugger console is used instead. If you want to debug your DLL, then launch the embedding process from your favorite debugger (gdb, WinDbg or Visual Studio for example) and you will see all debug messages in its output console.

===Beware of DllMain()!===

The body of a <tt>DllMain()</tt> function is an '''extremely''' dangerous place! This is because the order in which DLLs are unloaded when a process is terminating is unspecified. This means that the <tt>DllMain()</tt> for your DLL may be called when other DLLs containing functions that you call when de-initializing your DLL have already been unloaded. In other words, you can't put shutdown code inside DllMain(), unless your shutdown code only requires use of certain functions which are guaranteed to be available (see the Platform SDK docs for more info).

In particular, if you are writing a DLL that's statically linked with Haskell, it is not safe to call <tt>hs_exit()</tt> from <tt>DllMain()</tt>, since <tt>hs_exit()</tt> may make use of other DLLs. (For example it causes finalizers to be run and a finalizer may need to make use of a function in some other DLL.)

A solution is to always export <tt>Begin()</tt> and <tt>End()</tt> functions from your DLL, and call these from the application that uses the DLL, so that you can be sure that all DLLs needed by any shutdown code in your <tt>End()</tt> function are available when it is called.

''The following example is untested but illustrates the idea. It would be good if someone could check over it or replace by a real life example.'' Suppose we have a DLL called '''Lewis''' which makes use of 2 Haskell modules '''Bar''' and '''Zap''', where '''Bar''' imports '''Zap''' and is therefore the ''root module'' in the sense of [https://downloads.haskell.org/~ghc/8.0.2/docs/html/users_guide/ffi-chap.html#using-your-own-main GHC user's manual section 11.2.1.1]. Then the main C++ unit for the DLL would look something like:

  // Lewis.cpp -- compiled using GCC
  #include <Windows.h>
  #include "HsFFI.h"
  
  #define __LEWIS_DLL_EXPORT
  #include "Lewis.h"
  
  #include "Bar_stub.h"  // generated by GHC
  #include "Zap_stub.h"
  
  BOOL APIENTRY DllMain( HANDLE hModule, 
                         DWORD  ul_reason_for_call, 
                         LPVOID lpReserved
                        ){
    return TRUE;
  }
  
  extern "C"{
  
  LEWIS_API HsBool lewis_Begin(){
    int argc = ...
    char *argv[] = ...
    
    // Initialize Haskell runtime
    hs_init(&argc, &argv);
    
    // Tell Haskell about all root modules
    hs_add_root(__stginit_Bar);
    
    // do any other initialization here and
    // return false if there was a problem
    return HS_BOOL_TRUE;
  }
  
  LEWIS_API void lewis_End(){
    hs_exit();
  }
  
  LEWIS_API HsInt lewis_Test(HsInt x){
    // use Haskell functions exported by
    // modules Bar and/or Zap
    
    return ...
  }
  
  } // extern "C"

and some application which used the functions in the DLL would have a <tt>main()</tt> function like:

  // MyApp.cpp
  #include "stdafx.h"
  #include "Lewis.h"
  
  int main(int argc, char *argv[]){
    if (lewis_Begin()){
       // can now safely call other functions
       // exported by Lewis DLL
       
    }
    lewis_End();
    return 0;
  }

<tt>Lewis.h</tt> would have to have some appropriate <tt>#ifndef</tt> to ensure that the Haskell FFI types were defined for external users of the DLL (who wouldn't necessarily have GHC installed and therefore wouldn't have the include files like <tt>HsFFI.h</tt> etc).

=== Setting up your build environment (Visual Studio Specific) ===
* If you haven't already done so, create a new windows environment variable called <code>GHC_HOME</code> and set it to <code>c:\ghc\ghc-6.4.2</code> or wherever you've installed GHC
* Create a directory eg <code>c:\dll</code> to store all your DLLs
* Add this to the <code>PATH</code> environment variable so that Windows will find your DLL at runtime (Also your path should contain <code>%GHC_HOME%\bin;%GHC_HOME%\gcc-lib</code> if you also want to compile from the command line)
* Create a new Visual Studio DLL project. For the purposes of this example, we will call this <code>Duma</code>.
* In the Solution pane, right click on <code>Duma</code> then select Properties &rarr; Build Events &rarr; Post-Build Event and add the following event:
        Command Line:        copy "$(TargetDir)Duma.dll" c:\dll
        Description:         Copying duma.dll
        Excluded From Build: No
* In the Solution Pane, rename the folder <code>Source Files</code> to <code>Code Files</code> and adjust the properties of this folder so that <code>.h</code> files are also filtered into it. (This is a good idea for any C++ project because it keeps the <code>.cpp</code> and <code>.h</code> together in the same list which makes editing a C++ unit a lot easier.)
* Also rename the folder <code>Header Files</code> to <code>Haskell Files</code> and change its filter to select <code>.hs</code> files.
* In the <code>Code Files</code> folder, create a text file called <code>Duma.def</code>, then select Properties &rarr; Custom Build Step &rarr; General and enter the following:
        Command Line: %GHC_HOME%\gcc-lib\dlltool -d "$(InputDir)Duma.def" -l c:\dll\libDuma.a
        Description:  Creating libDuma.a from .def
        Outputs:      c:\dll\libDuma.a
        Additional Dependencies:
This makes the functions you will export from your DLL visible to GHC and GCC. (The path to dlltool given above will need to be changed if you have installed GHC in a different place.)
* Also in the <code>Code Files</code> folder, create a text file called <code>ghc.bat</code> with the following content:
        echo off
        REM Optimized build
        %GHC_HOME%\bin\ghc.exe -fglasgow-exts -fffi -I. -#include Duma.h --make main.hs -O2 -optl-lDuma -optl-L"c:\dll"
        if errorlevel 1 goto failed
        echo Success :-)
        goto end
        :failed
        echo Failure :-(
        :end
(The above batch file is based on that kindly supplied by Neil Mitchell on the GHC mailing list.)

You may also want to use <code>-optl-mwindows</code> if you don't want Haskell to create a console window.
* In Tools &rarr; External Tools, click <code>Add</code> and specify the following:
         Title: &ghc
         Command: ghc.bat
         Arguments:
         Initial directory: $(ProjectDir)
Remember to tick the <code>Use Output Window</code> box so you can see what's happening on the output pane of Visual Studio.

After you've done all this, you can build your DLL as usual by hitting <code>Control-Shift-B</code> and then make your Haskell program that uses the DLL by using <code>Alt-t-g</code> (assuming that your <code>main.hs</code> is in the same directory as the C files). When you just make changes to your DLL, you can use <code>F5</code> as normal (the first time you do this you will have to type <code>main.exe</code> into the box where it asks you for the main executable to use).

If you later install a newer version of GHC, you only need to modify the GHC_HOME windows environment variable.

== Using GHC for DLLs in Excel ==

This part illustrates the preceding '''Beware of dllMain()!''' section of this document. It extends the information found in the [https://downloads.haskell.org/~ghc/8.0.2/docs/html/users_guide/win32-dlls.html#building-and-using-win32-dlls Building and using Win32 DLLs] article. For build instructions and base code, refer to this article.

=== Excel crash on Exit when using a GHC DLL ===

Calling shutdownHaskell from the dllMain function, as in the given example can cause Excel to crash on exit.

As explained in section '''Beware of DllMain()!''' of this article, it's safer to call startupHaskell and shutdownHaskell from outside DllMain.

=== Updated dllMain.c code ===

Here is an updated <code>dllMain.c</code> code with additional initialization and shutdown functions (tested).

<pre>
    #include <windows.h>
    #include <Rts.h>
    
    #define __ADDER_DLL_EXPORT
    #define ADDER_API _declspec(dllexport)
    
    extern void __stginit_Adder(void);
    
    static char* args[] = { "ghcDll", NULL };
                        /* N.B. argv arrays must end with NULL */
    
    BOOL STDCALL DllMain( HANDLE hModule, 
                          DWORD  ul_reason_for_call, 
                          LPVOID lpReserved
                      ){
      return TRUE;
    }
    
    ADDER_API BOOL adder_Begin(){
      startupHaskell(1, args, __stginit_Adder);
      return HS_BOOL_TRUE;
    }
    
    ADDER_API void adder_End(){
      shutdownHaskell();
    }
</pre>

=== VBA code for Dll initialization and shutdown ===

We must call <code>adder_Begin</code> before any call to the DLL exported functions and <code>adder_End</code> before the DLL is unload. Excel VBA provides us with two callback functions that seems appropriate for this: <code>Workbook_Open</code> and <code>Workbook_BeforeClose</code>.

Function declaration in Excel is extended to add the two initalization and shutdown functions. I put it in a new module so I can make them public. The code looks like this:

<pre>
    Public Declare Function adder Lib "adder.dll" Alias "adder@8" (ByVal x As Long, ByVal y As Long) As Long
    Public Declare Function adder_Begin Lib "adder.dll" () As Boolean
    Public Declare Sub adder_End Lib "adder.dll" ()
</pre>

The callback functions have to be defined in the <code>ThisWorkbook</code> module and look like this:

<pre>
    Private Sub Workbook_BeforeClose(Cancel As Boolean)
      adder_End
    End Sub
    
    Private Sub Workbook_Open()
      adder_Begin
    End Sub
</pre>

=== Known problems ===

If closing Excel is canceled the <code>Workbook_BeforeClose</code> function will be called and haskell will be shutdown leaving the Workbook open but with Haskell down. The application will crash on the next DLL function call. This is easy to reproduce, modify the WorkBook, close it without saving and press <code>Cancel</code>. Change some value to cause a GHC function to be called and Enjoy Excel crashing.

==Random Questions==
===Are FunPtr's stable?===
Yes. Once you've obtained a FunPtr the FunPtr remains valid until it is explicitly freed (ie the garbage collector will not break it). See [http://research.microsoft.com/~simonpj/papers/marktoberdorf/ Tackling the Awkward Squad] section 6.4.2

===Can I free a FunPtr from inside the function itself?===
Yes (unless you are on IA64, right now).  See [http://www.haskell.org//pipermail/glasgow-haskell-users/2006-March/009907.html this thread] (the later messages in particular) for more details.