C/Cpp

A better present from a worse past. Also odd Vulkan spec anomalies.

One of the most fundamental items in any system, software or otherwise, is to be able to identify something uniquely.

Using CMake to automatically detect, or clone fresh, and even pre-compile Catch for you.

While Microsoft’s MSVC may be synonymous with Windows development, there are others.

Making life easier through enum flags, structs and offsets, and recreating Fallout’s SPECIAL reliably, quickly, efficiently, and safely.

Previously we added tools for code coverage and static analysis via clang-tidy. Now comes the ability to perform better runtime testing through GCC and Clang’s sanitizer tools, and integrating them with CMake.

Code coverage gives the ability to determine which sections of code are used, and how much, helping to prevent issues from sections of code that aren’t run during tests and thus could potentially fail in production.

One of the most valuable basic types in computer science is the floating point type. The float is that allows for a massive range of storable values, at the cost of some precision after the value becomes large enough, due to the fact that floats can only store ~7.2 decimal digits. Thus, if we wish to keep a certain fixed amount or precision, we need to either put coded limits around the use of particular floats, or just create our own fixed point type.

To accomplish this, the program reads in the generated SPIR-V binary, and outputs a text file containing the data, but in 4 byte chunks, so that it can be used as if it were a uint32 array.