Thank you. I will merge the optlib-based Forth parser first.
--
Reply to this email directly or view it on GitHub:
https://github.com/geany/geany/issues/3557#issuecomment-1717625885
You are receiving this because you are subscribed to this thread.
Message ID:
Closed #3557 as completed.
--
Reply to this email directly or view it on GitHub:
https://github.com/geany/geany/issues/3557#event-10359642528
You are receiving this because you are subscribed to this thread.
Message ID:
@masatake thanks indeed for the performance data.
--
Reply to this email directly or view it on GitHub:
https://github.com/geany/geany/issues/3557#issuecomment-1716767844
You are receiving this because you are subscribed to this thread.
Message ID:
> I have evaluated the performance of the .ctags based Forth parser with
> https://github.com/universal-ctags/codebase.
Thanks! This will be totally fine for Geany.
--
Reply to this email directly or view it on GitHub:
https://github.com/geany/geany/issues/3557#issuecomment-1716100404
You are
I have evaluated the performance of the .ctags based Forth parser with
https://github.com/universal-ctags/codebase.
```
[yamato@dev64]~/var/codebase% ./codebase ctags --ctags ~/bin/ctags Forth
version: db9fe7e0
features: +wildcards +regex +iconv +debug +option-directory +xpath +json
> My personal (very arbitrary) benchmark of speed acceptability would be that
> there shouldn't be any significant lags when editing a 1000 LOC source on
> Raspberry Pi 4.
I just had a brief look at the parser and there are very few and simple regexes
so I don't expect any performance
> I've tried to compile the forth.c generated from forth.ctags and I got a
> compilation error in geany, then I supposed that it was because the ctags
> code was out of date in geany.
Yes, we are like two years behind I'm afraid :-(. In general we want to make an
update to the latest ctags
> @techee should comment on if the C file generated by optlib that I see is
> part of https://github.com/universal-ctags/ctags/pull/3812 can be directly
> used by Geany, that is beyond my pay grade.
I don't think there's any issue with these parsers (apart from possible speed
problems, depends
@masatake @elextr
I've tried to compile the forth.c generated from forth.ctags and I got a
compilation error in geany, then I supposed that it was because the ctags code
was out of date in geany.
Then I've synchronised the geany code with the latest ctags, this time it
compiled without
My [reply](https://github.com/geany/geany/pull/3377#issuecomment-1713642517) to
@farvardin noted that Geany does not import the optlib directory from ctags so
Geany probably does not support optlib parsers directly.
@techee should comment on if the C file generated by optlib that I see is
10 matches
Mail list logo
