description | gperf port to simple c89 with benign bits of c99/c11 |
owner | sylvain.bertrand@legeek.net |
last change | Mon, 12 Jul 2021 17:34:23 +0000 (12 17:34 +0000) |
URL | git://repo.or.cz/cgperf.git |
| https://repo.or.cz/cgperf.git |
push URL | ssh://repo.or.cz/cgperf.git |
| https://repo.or.cz/cgperf.git (learn more) |
bundle info | cgperf.git downloadable bundles |
content tags
|
|
README
You should not use gperf anymore, very probably. It "may" be still usefull in
use cases with _very_ intensive, time/memory critical, and massive, _really_
massive, keyword lists. And even there, you should seriously consider
alternatives which are saner and semantically optimized to your use case. And
nowadays we know that c++ is never a good idea: the elephant in the room is the
obvious c++ compiler implementation cost, which is a significant detriment to
foster "working" alternative compilers, not to mention it is very prone to the
rube goldberg machine syndrome.
Don't be a masochist trying to reverse engineer the heuristics from the code
first hand: Read gperfp.pdf before anything else.
This is a "port to _simple_ C89 with benign bits of c99/c11". It is a properly
namespace-ized (then "reuse-able" in any other project), "one compilation unit"
project: just compile all.c and link it to your libc and libm the way you want.
Of course, bugs were introduced while porting.