Forth: new parser

[farvardin]

see #3810

[masatake]

Run make -BC win32 at the top of the source dir.
The command line may update win32/ctags_vs2013.vcxproj and win32/ctags_vs2013.vcxproj.filters.
Make a commit for the updated files.

[codecov]

Codecov Report

Patch coverage: 25.00% and project coverage change: -0.04% ⚠️

Comparison is base (f7e27b4) 85.06% compared to head (99878da) 85.03%.
Report is 4 commits behind head on master.

Additional details and impacted files

@@            Coverage Diff             @@
##           master    #3812      +/-   ##
==========================================
- Coverage   85.06%   85.03%   -0.04%     
==========================================
  Files         226      227       +1     
  Lines       53857    53889      +32     
==========================================
+ Hits        45816    45824       +8     
- Misses       8041     8065      +24     

Files Changed	Coverage Δ
optlib/forth.c	0.00% <0.00%> (ø)
main/selectors.c	80.28% <85.71%> (+0.18%)	⬆️
parsers/fortran.c	96.11% <100.00%> (+<0.01%)	⬆️

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

[masatake]

We don't need this file anymore.

[farvardin]

yes, I understand. But couldn't it be possible to skip it anyway? Geany told me they wanted it to be pushed upstream before integrating it into their code, and on the other hand they can't handle the .ctags / optlib tags...

[masatake]

See geany/geany#3557 .

The .ctags is translated to C. So technically, it is possible to integrate the .ctags based Forth parser into Geany.

Let's see how Geany people say.

[masatake]

@farvardin we got a positive answer from Geany developers introducing an optlib-based parser to Geany.

Could you remove parsers/forth.c ?

If we recognize the optlib-based implementation is not enough, you can open a pull request implementing the parser with crafted-C-code in the future. We can re-implement the parser safely because we have the test case.

[farvardin]

@masatake ok, I've done it. There was a conflict merge, I hope I haven't deleted some of your code, but it seems fine from my side

[masatake]

Do you know any large (open) source code bases written in Forth.

I would like to add them to https://github.com/universal-ctags/codebase.
So we can evaluate the performance of the parser.

[masatake]

I push two commits to your branch.

[farvardin]

Do you know any large (open) source code bases written in Forth.

I would like to add them to https://github.com/universal-ctags/codebase. So we can evaluate the performance of the parser.

good idea.
Most forth systems are written in forth itself. Here are some open source samples and codes:

https://git.savannah.gnu.org/cgit/gforth.git/tree/
https://git.sr.ht/~vdupras/duskos/tree/master/item/fs
https://gitlab.com/b2495/uf/-/blob/master/uf.f?ref_type=heads
https://sourceforge.net/p/forth-4th/code/HEAD/tree/trunk/4th.src/demo/
https://github.com/flagxor/ueforth/tree/main/examples
https://github.com/flagxor/ueforth/tree/main/common

some files are quite small, but others might be good candidates

[masatake]

Added Forth based source trees to the our codebase.
See universal-ctags/codebase@df32215

[masatake]

You removed .forth from the map. I guess you mistakenly removed it.
So I will add .forth again. If you really want to remove the file extension, please, make a pull request after I merge this one.

[masatake]

Thank you.

[farvardin]

@masatake thank you for your help and for this inclusion in ctags!