- Sep 02, 2008
-
-
Erwan Jahier authored
-
Erwan Jahier authored
-
- Sep 01, 2008
-
-
Erwan Jahier authored
simple, and also avoids 3 shift/reduce conflicts. It also make the pragma stuff more homogeneous and simple to explain in the manual. Moreover, pramgma are no more attached to AST nodes, but to lexemes.
-
Erwan Jahier authored
-
Erwan Jahier authored
-
- Aug 29, 2008
-
-
Erwan Jahier authored
-
Erwan Jahier authored
internal errors.
-
Erwan Jahier authored
around the rigth-hand-side.
-
Erwan Jahier authored
Note that by polymorphic here I mean *really* polymorphic, since they can handle tuples, which is no the case of, let's say, "<".
-
Erwan Jahier authored
splitting expressions.
-
Erwan Jahier authored
-
- Aug 28, 2008
-
-
Erwan Jahier authored
-
Erwan Jahier authored
-
Erwan Jahier authored
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>>;
-
- Aug 26, 2008
-
-
Erwan Jahier authored
+ enhance error msg (which helped finding the bug, but that migth also be useful for ed-users...).
-
- Aug 25, 2008
-
-
Erwan Jahier authored
-
Erwan Jahier authored
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;
-
- Aug 22, 2008
-
-
Erwan Jahier authored
enum nor a bool.
-
- Aug 21, 2008
-
-
Erwan Jahier authored
prefixed by "_".
-
Erwan Jahier authored
-
- Aug 20, 2008
-
-
Erwan Jahier authored
-
Erwan Jahier authored
definitions in their order of creation. The rationale is purely aesthetic...
-
- Aug 19, 2008
-
-
Erwan Jahier authored
-
Erwan Jahier authored
-
Erwan Jahier authored
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.
-
Erwan Jahier authored
-
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.
-
- Jul 23, 2008
-
-
Erwan Jahier authored
to avoid name clashes in the lic.
-
- Jul 22, 2008
-
-
Erwan Jahier authored
-
Erwan Jahier authored
-
- Jul 18, 2008
-
-
Erwan Jahier authored
behaves in the same manner on all configurations.
-
Erwan Jahier authored
account into the expected output of the non-reg tests.
-
Erwan Jahier authored
it breaks non-reg tests when executed in the original directory.
-
- Jul 17, 2008
-
-
Erwan Jahier authored
test/should_work/Pascal/t1.lus + typos
-
- Jul 08, 2008
-
-
Erwan Jahier authored
-
Erwan Jahier authored
lexing nightmares in lic2loc.
-
Erwan Jahier authored
to avoid priority errors.
-
Erwan Jahier authored
iterators (e.g., "Lustre::plus" instead of "Lustre::+") in order to make the life of lic3loc easier.
-
Erwan Jahier authored
to avoid priority errors.
-
Erwan Jahier authored
to avoid priority errors.
-