Amir Plivatsky

> I guess if this is expected behavior then there is no bug. It is not a "bug" - it is due to a huge number of disjuncts. Most CPU...

> I would like to have the link-generator to use the same user-interface as link-parser: so that one could type in "John * * * by the Red Sea." have...

Could you create an LG dictionary on the fly, parse (or generate) a "sentence", and then use the linkage? BTW, do links ever need to be crossed for command descriptions?

I said: > we need an external dictionary that lists the word's grammatical features. By external dictionary, I meant something like a database derived from Wiktionary and other similar resources....

You're right. However, in the current state of `link-generator`, `lt` might be its most useful language since it has a small dictionary. `en` is currently extremely slow for sentences with...

The problem with PCRE2 in compilers that don't support c11 threads happens only with multi-threaded programs that use the LG library in different threads simultaneously. I think most users never...

The code to set lw or rw (that were once `size_t`) to SIZE_MAX has been removed long ago. Possible solutions: 1. In `partial_init_linkage()`, memset with `1` and change the assert()...

In the distributed LG version 5.12.4, the type of `yy_buf_size` is `int`. So it seems your build generates it from `pp_lexer.l` using an old version of `flex` (or equivalent). Try...

> It looks like this bug: [westes/flex#118](https://github.com/westes/flex/issues/118) This is another bug, regarding `yyleng`. In our case, the problem is with the types of `yy_n_chars` vs `yy_buf_size`, which traditionally was `yy_size_t`...