- Jul 03, 2019
- Jul 02, 2019
-
-
erwan authored
-
- Jul 01, 2019
-
-
erwan authored
-
- Jun 26, 2019
-
- Jun 25, 2019
-
- Jun 24, 2019
-
- Jun 21, 2019
- Jun 20, 2019
- Jun 19, 2019
-
-
erwan authored
Basically, the idea is to parse the result of the registred ('s -> string) function. For instance if the user define 'v and 'v printer as follows: type state = { a : int ; b : float } let state_to_string s = Printf.sprintf "x=%d y=%f" s.v1 s.v2 pid_x and pid_y will be used as output var names in the RIF outputs. If the user provide no name: let state_to_string s = Printf.sprintf "%d %f" s.v1 s.v2 some names will be invented (pid_v0 and pid_v1)
-
erwan authored
All the get_* functions (that are of no interest for users) are now in the Register module.
-
erwan authored
Things that are currently broken: - the ability to init vars in the dot - controling the name of local vars in the rif output
-
- Jun 17, 2019
-
-
erwan authored
The idea is to use the Obj module (arg !!!), which is safe thanks to the fact that there is now only one register function, which forces all the 'v to be bound to the same type.
-
- Jun 14, 2019
-
-
erwan authored
-
- Jun 12, 2019
-
-
erwan authored
But I bumped into the "value restriction" limitation https://stackoverflow.com/questions/22507448/the-value-restriction Indeed, I need to store functions of 'v in some tables (or references), And tables are necessaryly weakly polymorphic ! https://v1.realworldocaml.org/v1/en/html/imperative-programming-1.html#side-effects-and-weak-polymorphism
-
- Jun 11, 2019
-
-
erwan authored
-
erwan authored
Indeed, by using the Env.nset and Env.nget defined in 0d6575a7 a pb that was hided by the use of Env.set and Env.get was triggered. The bug was that variables initialisations were done several times. In sasa.ml, the way I was updating the Env.t by iterating on the variables was forcing to "close" expressions that were calling init functions.
-
- Jun 06, 2019
-
-
erwan authored
-
erwan authored
More precisely, they were not consistent by the behavior of -custd mode. Indeed, It was returning the values of variables after the step is performed. In the custom demon mode, sasa returns Enab and variable values before the Activate is computed by the demon. Chosing one behavior or the other is arguable ; the main advantage of this choice is that we don't miss the initial values.
-
erwan authored
-
- May 29, 2019
-
-
erwan authored
-
- May 28, 2019
-