cauldron VS Criterion

I've previously written an algorithm that generates random floats in any [a,b], which can generate all possible floating point values, including subnormals, with the proper probability, and does so quickly for any choice of a and b. [0]

[0] https://github.com/camel-cdr/cauldron/blob/main/cauldron/ran...

The major advantage here is that you don't need to parse a dsl, and you can still have formatting options. A final api would probably use automatic compound literal struct arguments to implement default arguments with names parameters.

Type detection should also be possible, although you would need to register all print functions in a global macro.

This is just a proof of concept: https://github.com/camel-cdr/cauldron/blob/main/ideas/fmt.c

This is just a proof of concept: https://github.com/camel-cdr/cauldron/blob/main/ideas/fmt.c

It really depends on your use case, but I've written a header only PRNG library that might be interesting to you. I've also held a presentation about it, if you are interested in the specifics: "How computers generate random numbers (A guide for programmers)"

I've put it through an adapted version of testgauss.c, and it passed the test.

The entire romu-random.org family is faster than xoshiro256++, atleast in my benchmark:

Now for the self promo: If you are interested in random number generation, check out my presentation on the topic: https://www.youtube.com/watch?v=VHJUlRiRDCY You can also check out my random number library: https://github.com/camel-cdr/cauldron/blob/main/cauldron/random.h

For my benchmarking library, I use macros to tell the compiler not to optimize away a value, pre-running the benchmark to "warm up" the CPU/scheduler and calculate the average and deviation of multiple runs of the benchmark.

I really like Google Test, but am planning on doing some embedded development in C, where I sometimes find it awkward to test C code using a C++ library.

Therefore, I wrote a small unit test library closely mimicking Google Test. It consists of two source files, "rktest.c" and "rktest.h", and is about 1k lines of code and written in C99.

It uses a trick for self registering tests by placing pointers to the unit test functions into a known place in program memory, that I first learned about from https://github.com/christophercrouzet/rexo/ and https://github.com/Snaipe/Criterion/.

I have been using criterion on a recent project and enjoying it.

My school uses Criterion (doc). source code

Otherwise I use criterion https://github.com/Snaipe/Criterion, since a few cases can't be checked properly in python (or are a hassle to do)

Try this link for setup in doc.

https://github.com/Snaipe/Criterion < - repository for the unit-testing library.