gperf port to simple c89 with benign bits of c99/c11
No history found.
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.
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.
Hints:
Before first commit, do not forget to setup your git environment:
Clone this repository using HTTP(S):
Clone this repository using ssh (do not forget to upload a key first):
Clone this repository using git:
You are allowed to anonymously push to this repository.
This means that your pushed commits will automatically be transformed into a merge request:
Before first commit, do not forget to setup your git environment:
git config --global user.name "your_name_here"
git config --global user.email "your@email_here"
git config --global user.email "your@email_here"
Clone this repository using HTTP(S):
git clone https://rocketgit.com/user/sylware/cgperf
Clone this repository using ssh (do not forget to upload a key first):
git clone ssh://rocketgit@ssh.rocketgit.com/user/sylware/cgperf
Clone this repository using git:
git clone git://git.rocketgit.com/user/sylware/cgperf
You are allowed to anonymously push to this repository.
This means that your pushed commits will automatically be transformed into a merge request:
... clone the repository ...
... make some changes and some commits ...
git push origin main
... make some changes and some commits ...
git push origin main
RocketGit
Rocket your launch!
Rocket your launch!