jannick0

> The number of testcases failing on msys2 is now below 100. This is really good news - congratulations! > One of them because of this commit (https://core.tcl-lang.org/tcl/info/921cc1eb98e51b90). I personally...

@jafl @Explorer09 Apart of rather cosmetic things, could you please explain * under which circumstances `number_to_move` is non-positive here? As always, context matters. * if you checked that there is...

Great discussion! @jafl John, * I would suggest to run the `for` loop/`memcpy`/`memmove` only if `dest!=source` which in this context is certainly a harmless condition. (BTW: A reason for my...

Sorry for having been a bit sloppy. I wanted to ask you if you could run various flex scanners with your mega token example 1. flex 2.6.4 - current release...

Would that issue disappear by replacing `malloc` by `calloc`, which by default zero-initializes? If implemented, then only non-zero member initializations would be needed.

This should be fixed by PR #295 where all internal flex structures are zero-initialized.

> `Making all in tests` > `...` > `tests/ruleset.am:4: error: bad characters in variable name '*_nr_SOURCES'` The error occurs for VPATH builds only I believe. If you built in the...

For a VPATH build `ruleset.sh` shoud be run in the src test dir, i.e. `cd $(srcdir)` first (from one of my commits I am working on): ~~~diff ------------------------------ tests/Makefile.am ------------------------------...

I would rather consider this a bug if flex does not process the very skeleton which is compiled into flex.

Ouutsh - This is getting tricky here, since ´mkskel.sh´ envokes the shell (incl. the internal field separator), `sed` and `m4` with all their supposed EOL treatment (inherited from the compilation?),...