-
This blocks (at least) issues #6, #8, #9, #14, #16, #17, #39, #50, #52, #55.
-
Is it possible for the lexer to run in different modes, where in one mode something might be recognized, and it in another it would not?
For example, when lexing
`red AND blue`
A lexer runnin…
-
Hi,
It seems your lexing loses the last parameter of an assoc.
It seems to be fixable by this in glical_kernel in the Lexing module (I am too lazy to make a pull request for such a small fix):
```
…
-
Currently the REPL is very basic.
It uses basic pattern matching features on larger variable contents.
It's about to time to implement a lexer and parser to more accurately scan the line being enter…
-
Pull request coming to add support for incremental lexing.
It requires small changes to the existing runtime (but breaks no API's)
I've pasted the doc on how it works below as a starting poi…
-
I'm trying to upgrade from v2 to v3 due to an issue with being unable to escape a string value that was interpreted as a variable. However I now find myself in the exact opposite situation of having t…
-
Currently, we completely parse the current source file three times on almost every keypress.
- Once, for the autoedit strategy,
- then again for the syntax highlighter, and
- finally, to typecheck the…
-
Throughout I am utilizing CakeML v2274.
Given two programs, one with and one without nested parentheses in case statements:
```sml
fun fib n =
case (n = 1) of
True => 1
| False =>
case (n =…
-
```
It seems there is no EOF rule in PLY right now, to match the end of file,
dirty hacks must be used.
What version of the product are you using? On what operating system?
V3.3 on Linux
```
Orig…
-
Current state:
```
>> [#a@b]
== [#a @b] ;> #a/b
*** Syntax Error: (line 1) invalid issue at #a/b
*** Where: case
*** Stack: load
>> #@
*** Syntax Error: (line 1) invalid issue at #@
*** Wher…
Oldes updated
2 years ago