-
Update the wiki with all the necessary informations pertaining to github commit breakdown, grammar implementation in the bison file, matching within the flex file, etc. This will ensure a stronger bas…
-
On fraction, result depend on **times** sign (*like casio*) :
* 88/2(1+2) ) = 14.66
* 88/2*(1+2) = 132
the input / mathprint is correct.
But I found this quite inconsistence.
-
If there is a complex code on the client-side which can build a query object, it doesn't make sense to downgrade it into a string than reparsing it on the server-side. It would be nice to have an opti…
fekad updated
4 years ago
-
There has been some issues with Coco/R (#43, #159) and it is not actively maintained any more. The filter code should be ported to another framework. This has been discussed before: akrennmair/newsbeu…
-
Hello
I have a question regarding operator precedence. I have the following p4 representation (p4_shift_order) with this expression tree:
```c
control ingress(...) {
apply {
bit tmp…
-
Why not use antlr4 to describe the Grammar?
-
(with Bison v3.4.1, at least)
The default `` implementation in bison-complete mode looks like this:
```
if (matcher().at_end())
{
return yy::parser::symb…
-
I had small technical questions for the compiler:
- Do we have to build it with C++? If not, is Java supported on the testing machines?
- Are we limited to use yacc / lex? If not, are there any rest…
-
Currently RDFTerms (Literals, IRIs and prefixed IRIs) are represented as strings.
I suggest to use the RDF/JSON representation for RDF values.
Also, prefixed IRIs should be distinguished from IRIs.
…
iddan updated
4 years ago
-
Would it be possible to use glslang as a backend for a scintilla lexer/api (syntax highlighting / live syntax checking)? If so, where would I have to start deriving own classes?