single-file public domain libraries

library | documentation | description --------------------- | -------- | ------------- | -------------------------------- fts_fuzzy_match.h | readme blog | SublimeText inspired fuzzy string matching in C++ fts_fuzzy_match.js | readme blog demo | Fuzzy string matching in JavaScript

My personal take on STB style file libraries. Small librabries in one or two files that can be trivially drag'n'dropped into an existing project.

No convoluted build systems. No dependency rabbit holes. Easy to read, easy to use.

All source code is public domain. Do whatever you want.

My initials; Forrest Thomas Smith.

Several! C++ is the baseline. Multiple language implementations are provided where appropriate.

Because "proper" open source C code is full of gross macros and defines. I'd rather write simple code in a C++ namespace and call it a day.

My opinion is that portability can be achieved in two ways. One, include a dozen defines and macros to let users turn knobs on or off resulting in a million permutations. Two, provide the simplest possible implementation that can be trivially modified by users to meet their specific needs. I prefer writing and using the second.

There are also cases where user modification is to be expected. For example a string processing algorithm or any 3d math. Users can and should use their existing string and vector/matrix libraries. In such cases I prefer to provide basic implementations that can be easily modified by users to fit the mold of their project. I believe that to be better than crufty, inscrutible macro schemes.

Core libs linked on this page are written in C++ but very near to C.

Test code is full of C++11, STL, and all kinds of icky things. Tread with caution!

Files in code/util are fully independent but not significant enough to warrant root status. They may be C++ oriented and may use C++11/14 features.