To share signals between host and calls, it is possible to use an object interface for program descriptions too. It is then possible to provide an instanciation methode p#create to the user and an instanciation function p#create_run that take different arguments. I one case i takes only signal initial values and in the other case it takes signals structures.

Just beware that p#create_run must ignore animate

see this example

It could optmise the futur interleaving of tasks and grc representation

It might be nice to document some non-trivial parts of the code like

• comment surf / depth
• interleaving
• memoization parts

When I try some of the examples (TodoMVC for instance) I get the following in the Javascript console:

uncaught exception: 0,248,Assert_failure,-11,0,src/runtime/runtime_misc.ml,56,19 <unknown>

I've tried on Chrome, Safari and Firefox

see the title...

Several things :

• What is the input value for an output signal ?
  • callback function ?
  • default value ?
• What is the consequence on the run statement ?

Warning: integer overflow: integer 0x3ffffffffffdffff (4611686018427256831) truncated to 0xfffdffff (-131073); the generated code might be incorrect.
Warning: integer overflow: integer 0x3fffffffffffffef (4611686018427387887) truncated to 0xffffffef (-17); the generated code might be incorrect.
Warning: integer overflow: integer 0x3fffffffffffff7f (4611686018427387775) truncated to 0xffffff7f (-129); the generated code might be incorrect.
Warning: integer overflow: integer 0x3ffffffffffffbff (4611686018427386879) truncated to 0xfffffbff (-1025); the generated code might be incorrect.
Warning: integer overflow: integer 0x3fffffffffffdfff (4611686018427379711) truncated to 0xffffdfff (-8193); the generated code might be incorrect.
Warning: integer overflow: integer 0x3fffffffffffbfff (4611686018427371519) truncated to 0xffffbfff (-16385); the generated code might be incorrect.
Warning: integer overflow: integer 0x3fffffffffff7fff (4611686018427355135) truncated to 0xffff7fff (-32769); the generated code might be incorrect.
Warning: integer overflow: integer 0x3ffffffffffeffff (4611686018427322367) truncated to 0xfffeffff (-65537); the generated code might be incorrect.
Warning: integer overflow: integer 0x3fffffffff7fffff (4611686018418999295) truncated to 0xff7fffff (-8388609); the generated code might be incorrect.
Warning: integer overflow: integer 0x3fffffffffbfffff (4611686018423193599) truncated to 0xffbfffff (-4194305); the generated code might be incorrect.
Warning: integer overflow: integer 0xb800000000 (790273982464) truncated to 0x0 (0); the generated code might be incorrect.
Warning: integer overflow: integer 0x3ffffffffbffffff (4611686018360279039) truncated to 0xfbffffff (-67108865); the generated code might be incorrect.
Warning: integer overflow: integer 0x500000000 (21474836480) truncated to 0x0 (0); the generated code might be incorrect.
Warning: integer overflow: integer 0x80000000 (2147483648) truncated to 0x80000000 (-2147483648); the generated code might be incorrect.
Warning: integer overflow: integer 0x4000000000 (274877906944) truncated to 0x0 (0); the generated code might be incorrect.
Warning: integer overflow: integer 0x3fffffdfffffffff (4611685880988434431) truncated to 0xffffffff (-1); the generated code might be incorrect.
Warning: integer overflow: integer 0x1000000000000 (281474976710656) truncated to 0x0 (0); the generated code might be incorrect.

Possibily generated by PPX

It's naive but the code size reduction should be consequent

• improve the language with gathered signals to fix this
• tried just by changing the type of events in ocaml to lists but then it's not
  possible anymore to get environnement values at anytime
• add a syntax :

input items (fun items x -> x :: items);

and

input (newit : inputElement Js.t)
  (onkeydown (
      fun omm ev ->
        if newit##.value##.length > 0 && ev##.keyCode = 13 then
          newit##.value :: omm else omm) [])
;

or even

let%sync prog ?(items=fun items x -> x :: items) = ... 

The scope of the type variables is weird, see this example :

let make v1 v2 = v1, v2 in
let a =
  let (x, y) : ('a * ('a -> 'b -> 'a)) =
    ("", fun acc x -> acc ^ x)
  in make x y
in
let b =
  let (x, y) : ('a * ('a -> 'b -> 'a)) =
    ([], fun acc x -> x :: acc)
  in make x y 
in a, b

see eb9da6d

• Language documentation
  • Call Documentation "Syntax"
  • Information about the single syntax elements especially the statements.
  • General informations like how the JS events and Pendulum signals interact.
• Web based Esterel engine : an input/output area like reacting on simple mouse clicks
  with a simple source text field.
• Comments : More educational comments in the code of the examples.

(Thx Ben for those remarks)

• add first class machines (necessary)
• maintain signals values or presence informations between steps
• gathering operators at signal definitions (several emission of the same signal at the same instant
• pre
• n-ary parallel operator and/or gathering (at signals definition)

Use https://github.com/ocaml/ocaml/blob/trunk/parsing/parsetree.mli#l305

The problem of the run statement meets the one of locals and can be handle in the same way in GRC :

• put the Run induction case in grc and in depth / surface do
  • if i'm not selected,
    • I Initialize the machine with the corrects inputs then I run one step
  • If I am,
    • I set present with the correct value every inputs that are actually present
    • I run one step
• About the code generation
  • All runs must define a global value outside of step (as local signals)
  • each run has a specific id

Problem : If there is any side effect in local signal definition expression, it will be executed when the synchronous program is instantiated, which is incorrect.

Solution : use Obj.magic 0 as value for local signals initialization instead of their actual expression.

It's gonna improve the research on the join of a test branch.
It can be None or Some.

From this code :

let%sync reactive_player =
  input play;
  input start_slide;
  input stop_slide;

  let cant_update = () in
  loop begin
    present play (atom (print_string "play"));
    pause
  end
  || loop begin
    await start_slide;
    trap t' (
      loop (
        present stop_slide nothing (exit t')
      ); pause
    );
    pause
  end

try setTimeout and requestAnimationFrames as global clocks

There might be a problem in signals emission / reception.

depends of #14