Repository files navigation

My single header libraries for C/C++.

Total libraries: 5
Total lines of C code: 4487

Windows doesn't have standard directories where librarieslive. That makes deploying libraries in Windows a lot morepainful than open source developers on Unix-derivates generallyrealize. (It also makes library dependencies a lot worse in Windows.)

There's also a common problem in Windows where a library was builtagainst a different version of the runtime library, which causeslink conflicts and confusion. Shipping the libs as headers meansyou normally just compile them straight into your project withoutmaking libraries, thus sidestepping that problem.

Making them a single file makes it very easy to justdrop them into a project that needs them. (Of course you canstill put them in a proper shared library tree if you want.)

Why not two files, one a header and one an implementation?The difference between 10 files and 9 files is not a big deal,but the difference between 2 files and 1 file is a big deal.You don't need to zip or tar the files up, you don't have toremember to attachtwo files, etc.

Each file has documentation, basic ussage description andexamples at the top of the file. In addition each API function,struct and member variables are documented as well.Finally each library has a corresponding test file inside thetest directory for additional working examples.

Personally I primarily use C instead of C++ and since I want tosupport both C and C++ and C++ is not useable from C I therefore focuson C.

I use C89 instead of C99/C11 for its portability between different compilersand accessiblity for other languages.

• Sean Barretts single header libraries
• Other single header libraries
• enkiTS: source implementation for mm_sched.h
• Webby: source implementation for mm_web.h