-
Erwan Jahier authored
as many new local variables as necessary so that an expression is made at most of one operator. The rational for that is to obtain a lic code that is trivial to clock check (nested node calls, for example, make it less simple). The old behavior can still be obtained using --keep-nested-calls. During that change, I realised that I did not clock check asserts. Hence, I have also added this check.
Erwan Jahier authoredas many new local variables as necessary so that an expression is made at most of one operator. The rational for that is to obtain a lic code that is trivial to clock check (nested node calls, for example, make it less simple). The old behavior can still be obtained using --keep-nested-calls. During that change, I realised that I did not clock check asserts. Hence, I have also added this check.
evalType.mli 434 B
(** Time-stamp: <modified the 18/08/2008 (at 11:21) by Erwan Jahier> *)
open CompiledData
(** Evaluates the type of an expression. *)
val f : id_solver -> val_exp_eff -> type_eff list
(* Returns the type of an expression. Note that this function uses
an internal table, and therefore it should not be called before
the type checking has been done (by the function f above).*)
val val_exp_eff : val_exp_eff -> type_eff list