"Ross Paterson"
...
But I don't understand how the API versioning works, when the version is selected by the interpreter rather than the DLL.
Modules that have 'primitive'-based extension DLLs associated with them are required to use a 'needPrims_hugs <api version>' declaration to signal its loading. That version number is all that's needed. This doesn't deal with extension DLLs generated by the new FFI, where the interpreter simply assumes a specific version number. There aren't too many of those DLLs floating about (yet), which is why I mentioned that these will simply have to be re-compiled for now. The DLL external interface will have to be extended to also convey what HugsAPI version number the exported primitives assume. ---sigbjorn