Rochus Keller

Welcome. > Would you consider publishing x86_64 with lua enabled? I'm only using the 32 bit version and never compiled/testet it on 64 bit. Likely some modifications are required to...

The development up to now is mostly driven by my personal demand. I use the tool for my projects on a daily basis since nearly ten years. With the HTML...

I implemented columns in DoorScope but not in CrossLine because I had no need for them for the last ten years; though I used columns in Ecco a few times....

That looks like a typical lexer production. EbnfStudio is only a parser generator tool, useful for LL(1) grammars with LL(k) exceptions.

Thanks. Looks like rather cosmetic warnings by the compiler which I usually ignore or suppress (e.g. -Wno-reorder). The issues causing a segfault should be fixed of course.

> that you have some extensions that isn't documented Well, I wouldn't consider the project to be a complete project ready for everyones use; it's work in progress and I...

Welcome. Note that I added an edit to my answer. > this project to also generate tree-sitter grammars Not sure whether this works without a full redesign, because EbnfStudio is...

> Would be nice if we could generate a Lua parser with CocoR That's actually already implemented. Have a look at https://github.com/rochus-keller/LjTools/blob/master/LuaLexer.cpp and https://github.com/rochus-keller/LjTools/blob/master/LuaParser.cpp.

> ../LuaJIT/src/LuaJit.pri You can ignore that. The code means: "if you find LuaJit.pri, then use it and link with dl, otherwhise ignore it and link with the full luajit so"....

I used the original grammar from https://www.lua.org/manual/5.1/manual.html#8 which declares all binary operations in the same production and terms/factors/primaries are all combined in the 'exp' production. That didn't bother me because...