Gerwin Klein
Gerwin Klein
The 1.8.0 release initially failed because of javadoc errors, most of which are fixed now. To make sure we spot these earlier next time, we should enable doclint and javadoc...
In the early days JFlex used to have a performance benchmarking suite, in particular to compare to JLex and to figure out the trade-offs for different scanning engine options (pack/table/switch...
As discussed in issue #211 and PR #213, the JFlex generator is currently not thread safe. It'd be nice for larger projects if multiple concurrent build invocations could be supported....
**Reported by briansmith on 2006-10-29 06:30 UTC** My suggestion is simple: 1. Everywhere that the code generate currently generates `zzBuffer[xxxx]`, it should instead generate `zzCharAt(xxxx)`. 2. The standard skeletons define...
Now that github workflows are free for public repos, it is probably easier to maintain and easier to interact with if we run the travis CI tasks directly on github....
**Reported by *anonymous on 2010-10-17 12:10 UTC** In the lexer you often return the new state, but that's not required. I'd like to be able to catch all cases. Those...
[SPDX](https://spdx.org) is a good way to keep track of which licenses are being used in a project and I think it would make sense to use them consistently in JFLex...
For some time in the future when there is time for such things: At some point we should refactor the front-end (mostly `LexParse.cup`) to produce a clean abstract syntax tree...
The current unit testing in JFlex is a bit thin, mostly because the cost/benefit ratio of writing those single test cases is fairly low. We should use property-based unit tests,...