GHCJS now runs Template Haskell on node.js - Any interest in out of process TH for general cross compilation?
john at repetae.net
Thu Jul 3 20:47:51 UTC 2014
In case anyone wanted to start writing haskell android code now, jhc
fully supports android as a target. here is an app made with it
this was made with Kiwamu's ajhc branch but code has been merged back
into the main tree.
On Wed, Jul 2, 2014 at 5:54 PM, Carter Schonwald
<carter.schonwald at gmail.com> wrote:
> This would probably be a great boon for those trying to use haskell for
> Android and IOS right? how might the emulation setup work for those?
> On Wed, Jul 2, 2014 at 2:20 PM, Carter Schonwald
> <carter.schonwald at gmail.com> wrote:
>> wow, this is great work!
>> If theres a clear path to getting the generic tooling into 7.10, i'm all
>> for it :) (and willing to help on concrete mechanical subtasks)
>> On Wed, Jul 2, 2014 at 12:14 PM, Luite Stegeman <stegeman at gmail.com>
>>> hi all,
>>> I've added some code   to GHCJS to make it run Template Haskell
>>> code on node.js, rather than using the GHC linker. GHCJS has supported TH
>>> for a long time now, but so far always relied on native (host) code for it.
>>> for everything (another is that Cabal Setup.hs scripts need to be compiled
>>> Now besides the compiler having to do twice the work, this has some other
>>> code, which means packages like unix or Win32 show up somewhere, depending
>>> on the host environment. This also limits our options in choosing
>>> JS-specific packages.
>>> - The Template Haskell code runs on the host environment, which might be
>>> slightly different from the target, for example in integer size or operating
>>> system specific constants.
>>> Moreover, building native code made the GHCJS installation procedure more
>>> tricky, making end users think about libgmp or libiconv locations, since it
>>> basically required the same preparation as building GHC from source. This
>>> change will make installing much easier and more reliable (we still have to
>>> update the build scripts).
>>> How it works is pretty simple:
>>> - When any code needs to be run on the target (hscCompileCoreExpr,
>>> through the Hooks API new in GHC 7.8), GHCJS starts a node.js process with
>>> the thrunner.js  script,
>>> - GHCJS sends its RTS and the Template Haskell server code  to
>>> node.js, the script starts a Haskell thread running the server,
>>> its incremental linking functionality. The code for the splice, including
>>> dependencies that have not yet been sent to the runner (for earlier
>>> splices), is then sent in a RunTH  message,
>>> - the runner loads and runs the code in the Q monad, can send queries to
>>> GHCJS for reification,
>>> - the runner sends back the result as a serialized Template Haskell AST
>>> (using GHC.Generics for the Binary instances).
>>> All Template Haskell functionality is supported, including recent
>>> additions for reifying modules and annotations. I still need to clean up and
>>> push the patches for the directory and process packages, but after that, the
>>> TH code can read/write files, run processes and interact with them and make
>>> network connections, all through node.js.
>>> wondering if there's any interest in getting this functionality into GHC
>>> 7.10 for general cross compilation. The runner would be a native (target)
>>> program with dynamic libraries (or object files) being sent over to the
>>> target machine (or emulator) for the splices.
>>> Thanks to Andras Slemmer from Prezi who helped build the initial proof of
>>> concept (without reification) at BudHac.
>>> Glasgow-haskell-users mailing list
>>> Glasgow-haskell-users at haskell.org
> Glasgow-haskell-users mailing list
> Glasgow-haskell-users at haskell.org
John Meacham - http://notanumber.net/
More information about the ghc-devs