(And if anyone has an interest in contributing, please get in touch!)
(And if anyone has an interest in contributing, please get in touch!)
Please don't hesitate to ask us on the dev mailing list if you run into any problems. For one thing, we're planning on making some updates to the protocol spec soon, based mostly on the experience of the IJulia work. It would be great to have your input there as well, in case you spot something that wouldn't fit well the patterns you saw while doing the Haskell port.
And besides, this means I now have one less excuse to get off my butt and learn Haskell! :)
What about multiple definitions for functions depending on what kind of input is given. Like python has no tail recursion, but lisp does. Write a python function that gets transparently translated to lisp to utilize the features of the language.
You could perhaps have multiple language cores each communicating problems to one another via the common language of the notebook... but that's nothing more than any other text serialization route with all of the challenges therein.
Is IHaskell related to ihaskell-notebook? https://github.com/creswick/ihaskell-notebook
If anyone wants a good intro to the amazing stuff IPython can do, check this (~3hr) video out: http://pyvideo.org/video/1652/ipython-in-depth-high-producti...
Or, many examples of what the notebooks can do: http://nbviewer.ipython.org/
[0] http://andrew.gibiansky.com/blog/ipython/ipython-kernels/
Be sure to send a message to the IPython-dev mailing list if you're happy to recieve contributions and/or feedback (also from IPython developers).