It now takes  as first argument the whole list  of processes (not only
the enabled ones).

In  Algo.pf_info, the  action  field  is now  an  option  type (if  is
correspond to a process that has not been activated).

nb: does not really work yet.

Update: add the previous state in argument of the fault function.

New: add a fault functions to the Algo (to inject fault when a legitimate configuratiuon is reached).

nb: I needed to  split Main to avoid a Module self-loop  (as I need to
use do_step in Daemon).

The  rationale is  that the  Algo.spid that  gave processes  access to
their pid via their neighbors was a bit weird. Also, it makes the anonymity
of the algorithm more explicit: an access to the pid could appear anywhere
in the program, while now, the pid must be in state.t!

Now, if the  user needs the pid,  he must store it  explicitly in the
state via the initialization function.

To force that, I've changed the Register interface (and thus GenRegister)

The rationale is that:
- in lurette mode, they should be the same for all algos already
- in batch mode, action declarations are ignored anyway (except in custom mode)

as it is where they belong.

Indeed, during the explanations, it makes more sense to start with the state.

Doc: rework the documentation of the Algo API.

Add use it to add an oracle to the BFS

Took into account Erwan's comments and changed Register module such that the properties are computed on first call (except height that is computed on each call because it depends on the chosen tree's root)

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)

All the get_* functions (that are of no interest for users) are now in
the Register module.

Things that are currently broken:
- the ability to init vars in the dot
- controling the name of local vars in the rif output

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.

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

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.

Depending on the kind of network, we should raise an exception. Indeed
such information should not be available in anonymous networks.

We will add such checks later.