Commit 19da3459 authored by POGODALLA Sylvain's avatar POGODALLA Sylvain

Fixing issue #1

parent e831dcb6
......@@ -290,9 +290,10 @@ Lex_entries always ends with a ; and have the following form:
With the `lexicon` keyword, `lambda` (resp. `->`) is interpreted as
`lambda` (resp. `->`), whereas with `nl_lexicon`, `lambda`
(resp. `->`) is interpreted as `Lambda` (resp. `=>`). It is useful
when not interested in linear constraints in the object signature (as,
for instance, in the context-free lambda grammars).
(resp. `->`) is interpreted as `Lambda` (resp. `=>`). I.e., everything
is interpreted non linearly. It is useful when not interested in
linear constraints in the object signature (as, for instance, in the
context-free lambda grammars).
2. By lexicon composition as in:
```
......
......@@ -202,7 +202,7 @@ There are two ways to define a lexicon:
lex_entries
end
```
With the `lexicon` keyword, `lambda` (resp. `->`) is interpreted as `lambda` (resp. `->`), whereas with `nl_lexicon`, `lambda` (resp. `->`) is interpreted as `Lambda` (resp. `=>`). It is useful when not interested in linear constraints in the object signature (as, for instance, in the context-free lambda grammars).
With the `lexicon` keyword, `lambda` (resp. `->`) is interpreted as `lambda` (resp. `->`), whereas with `nl_lexicon`, `lambda` (resp. `->`) is interpreted as `Lambda` (resp. `=>`). I.e., everything is interpreted non linearly. It is useful when not interested in linear constraints in the object signature (as, for instance, in the context-free lambda grammars).
`Lex_entries` is a list of `lex_entry`, separated with a `;`. A `lex_entry` can be of the following forms:
* `abstract_atomic_type1, abstract_atomic_type2 := object_type;`
......
Markdown is supported
0% or
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment