But actually, it is possible to have node without output, so expression
without output clock is perfrectly possible, as in the following example :

node h(x : bool) returns ();
 var h : bool;
let
  h = false fby (not x);
tel

node f(x : bool) returns (y: bool);
var
  u:bool;
let
  y,u = (false, h(true), true) fby (true, x, h(false));
tel

Also, -eeb is now the default when using -ec.

It was generetaing wrong code in conjunction with -ec.

In particular, it was generating n-any "and" instead of binary "and".

Also, I needed (in L2LExpandEnum) to generated a Lic.ARRAY of const
instead of a Lic.Array_const_eff so that LicDump properly generated
ec code.

To do that, I have created a new dedicated module L2lExpandEnum, that
actually also deals with -eei (which was probably wrong, even if I
have not counter-exemple).

Use 1-hot encoding instead of log-encoding

I've fixed a bug in L2lExpandArrays that occurs on equation such as
  some_bool = (some_array1 = some_array2);

Also, I've rewritten Lv6Compile for more readability

Remove duplicated code when using SocMap.find and co

I've fixed that using memcmp, which should be fine since compared elements
are of the same types.

+ add a test that reveal a pb in the generated C code in lustre programs
that perform equalities on arrays.

Indeed, expressions such as "3.0-42.5" caused a syntax error, as the unary minus
of real constant was in hard in the lexer.  "3.0- 42.5" worked, but still.

The problem then was that LicEvalConst refused to eval "- 3.14", that was
parsed directly as a constant, and that is now a call to the unary minus.
I've added specific code to handle this case.

Otherwise, strange things sometimes happen.

The previous change fixed program that contains type decl such as :
type t1;
type t2 = t1;

but not

type t1;
type t2 = t1^2 ;

or

type t2 = { xxx : t1^2 ; yyy : t1^2} ;

And now it works.

To fix it, I have include the _ext.h file into the lustre_type.h one.

The previous change fixed program that contains type decl such as :
type t1;
type t2 = t1;

but not

type t1;
type t2 = t1^2 ;

or

type t2 = { xxx : t1^2 ; yyy : t1^2} ;

And now it works.

To fix it, I have include the _ext.h file into the lustre_type.h one.

Also, the simulation via the _loop.c file was failing in extern types were present
as O/I of the main (simulated) node.

Also, use rdbg instead of lurettetop to run the test.

which was not even compiling...

also:
 -2cw7: fix the generated script
 arduino dir: minor fixes

nb : i have changed the var name in the generated nodes, which was a bad idea
(=painful to get it rigth again).

I have duplicated the interpretation function SocExec.soc_step
into a CPS SocExecDbg.soc_step

One day I migth only keep the dbg one.

Reference Manual enhancements.

so that w7/lesar can help otawa/ilp to prune path in the binary.

nb : not working on the convertible example:
 - sometimes the module name still appear in the ident (enums)
 - clocks are not well supported by Lesar actually. More thinking is necessary.

Because otherwise, V4 ec tools behaves strangely.

The bug was appearing a node was called on a non base clock that was
existing in the called nodes (name clash). Typically, it occurs on
recursive node called on some non-trivial clocks.

Also, use maps instead of list to hold the substitution between
params and args.

var_info appears in
- node decl
- left var
- static args

not yet working. I commit as Ive fix a missing dep on WenOnId in the _oasis.

More precisely, transforms equations of the form

   y = x when Toto(c);

into

   x when Toto_c ;
   Toto_c=Toto(c);

Rationale: the << normal mode >> (i.e., not translating enums) was
not even accessible!