polymorphic operators.

For instance, when LicDumping expression such as

    map<<map<<+,4>>,5>>

an  alias  node was  created  for  "map<<+,4>>"  (to unnest  iterator
calls). Fut this node is intrically overloaded (polymorphic). In this
change, we  look at  the type this  innr call  is used to  generate a
specialised (mono-morphic) version of the node alias.

Note that we currently still generate type variable when users write

     node mymap = map<<+,4>>;

+ enhance  error msg  (which helped finding  the bug, but  that migth
also be useful for ed-users...).

The  idea  is  the  following:  each  time  a  nested  iterator  call
(map<<map<<n,3>>,4>>) is  encountered, we  create a fresh  alias name
(create_alias_name) ad we  add it in the node_alias_tbl.   At the end
of the  compilation, LicDump.dump_node_alias is  called, which prints
the definition of those node aliases.

For example, the expression  "map<<map<<n,3>>,4>>" is printed like this:

    map<<_node_alias1, 4>>

and later, the node alias is defined:

    node _node_alias1(x:int) returns(y:int); let y = map<<n,3>>(x); tel;

enum nor a bool.

prefixed by "_".

definitions in their order of creation. The rationale is purely aesthetic...

was used in  the local variables generated to  split expressions into
atomic expressions.

Indeed,  when  such an  intermediary  expression  is  inferred to  be
variable, it is  ok to consider that  it is on the base  clock. And I
was missing such a case.

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.

to avoid name clashes in the lic.

behaves in the same manner on all configurations.

account into the expected output of the non-reg tests.

it breaks non-reg tests when executed in the original directory.

test/should_work/Pascal/t1.lus

+ typos

lexing nightmares in lic2loc.

to avoid priority errors.

iterators (e.g.,  "Lustre::plus" instead of "Lustre::+")  in order to
make the life of lic3loc easier.

to avoid priority errors.

to avoid priority errors.

to avoid priority errors.

parenthesis, but after an equal sign, as in lv6.

profiles constain only named types.

Typically, instead of printing:

           node toto(x: int ^ 4) ...

print something like :

           type int4 = int ^ 4
           node toto(x: int4) ...

Moreover, in  order to  avoid name clashes,  we prefix all  user name
type by "_".

e.g., instead of

        type toto = toto { ... };

we now print

        type toto = struct { ... };

Add some tests with various kinds of expr that we can have after a when.

PredefEvelClock, in a similar manner as for type checking.

clock_info, and  therefore also  remove clock_info. The  rationale of
this  change is  that  it  makes things  slightly  simpler, and  more
homogeneous with what is done in type checking.