> Please have the parser accepted upstream first, even though its very simple > it adds work to updating ctags to check if a change breaks it. > > Also without `geany_` on the name, being a parser in Geany without an > upstream, it will break `scripts/update_ctags.py` (perhaps the script could > be more resilient, but on the other hand it indicates that an upstream parser > has been moved or renamed, so it _should_ stop).
I'm in the process of doing it, and the forth.c file had been converted to a forth.ctags for optlib. https://github.com/universal-ctags/ctags/pull/3810 There is an automated forth.c generated from the optlib code. It's located there: https://github.com/universal-ctags/ctags/blob/18f4f91fc18893a5e984bff3018e159b4e97c46f/optlib/forth.c I have problems to compile it, this is giving me those errors: ``` parsers/forth.c:44:12: error: ‘parserDefinition’ {aka ‘struct sParserDefinition’} has no m ember named ‘versionCurrent’ 44 | def->versionCurrent= 0; | ^~ parsers/forth.c:45:12: error: ‘parserDefinition’ {aka ‘struct sParserDefinition’} has no m ember named ‘versionAge’ 45 | def->versionAge = 0; ``` does geany handles optlib? https://docs.ctags.io/en/latest/optlib.html#translating-an-option-file-into-c-source-code-optlib2c -- Reply to this email directly or view it on GitHub: https://github.com/geany/geany/pull/3377#issuecomment-1713612398 You are receiving this because you are subscribed to this thread. Message ID: <geany/geany/pull/3377/[email protected]>
