Andrew Ray

Thanks. I've updated the example with option 1. and can use both c and ocaml based callbacks. I will probably add an attribute so you can choose between options 1...

Do you mean 1 avoids the dependency (if you don't need to use a callback)? On 5 Nov 2016 16:49, "yallop" [email protected] wrote: > I think the only real advantage...

Oh, this is an issue. The docs are correct for the new version, where we have renamed `ppx_deriving_hardcaml` to `ppx_hardcaml`. However, the version story is a problem as this now...

Initial thoughts; When you name a signal with the `(--)` operator (or similarly when you use `Scoped.naming` in a hierarchical context) those named signals can be printed in the waveform...

I think implementing the ocaml kernel on top of this will help expose all the required functionality. stdout/stderr (and potentially stdin) might need some thought.

Indeed, I definitely intend to port the ocaml kernel across and make it live here. (Not before the new year though...) Regarding MIME stuff it should just work.....98% of that...

Will do. I will ensure that everything that used to work in iocaml still does when I port it across, including mime, stdio stuff and whatever else I find (but...

Yeah - the stdio stuff has specific messages I seem to remember. In iocaml there's a bit of `dup2` magic followed by some ocaml threads that drain the channels and...