+ 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.

BTW, add a missing module (L2lCheckCKeyWord) introduced in the previous change
(necessary for the v6 rdbg plugin)

which was not even compiling...

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

with recursive clock depende ncies.

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.

generates unvalid C code.

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.