-
Is what is written here:
https://github.com/HedvigS/gramfinder-typology-of-terminnology-and-searching-OCRed-grammars/blob/master/Different%20aims%20and%20contributions
Something that others here @x…
-
@cyrillemidingoyi @kaby76
The Parser cannot able to parse successfully Access Statements like PUBLIC, PRIVATE etc. in the Fortran90 code.
This is the Fortran90 Grammar file:
https://github.c…
-
```
The StanfordParser supports a new model based on Compositional Vector Grammars. These
are comparative to the factored parser and faster. Should we switch the default variant
from factored to rnn w…
-
```
The StanfordParser supports a new model based on Compositional Vector Grammars.
These are comparative to the factored parser and faster. Should we switch the
default variant from factored to rnn…
-
I could not get an extended parser form (something like) `"$..key[?(@.sub == "bar"]` to work. Tried many forms. Then I started digging into the code and I ran across what I show below. It looks odd…
-
In the progsys problems 26 of the grammars contain:
::= ''|'=='|'>='|'
-
Hello @mdaines,
(_I hope you don't mind another issue_)
I think it would be awesome if there was a way to load sample grammars (and perhaps make it easy to submit them via PRs?). I'm thinking of…
-
Treat `bool`, `num`, `double`, and `int` as keywords.
> [!NOTE]
> It is not necessary to change the default colouring for these types.
These could be configured by the user, or by external theme …
-
There is no Shell language target. Hope to support shell target.
-
https://prometheus.io/docs/prometheus/latest/querying/basics/#modifier
![WX20230129-232434@2x](https://user-images.githubusercontent.com/490237/215336436-a2d84e4f-a550-43cf-ad13-62fe094a984b.png)