I’ve been tinkering around with a new one header library (having been inspired by the awesome stb libraries that @nothings created), a utf8 string library https://github.com/sheredom/utf8.h.
The utf8.h header adds some new utf8* prefixed functions that match the str* functions you would find in string.h, except that they are all written for utf8 exclusively. For example, utf8len will return the number of utf8 codepoints found in the provided utf8 string.
I’m quite particular about how I word the variables that are exposed via my APIs. I always prefix pointers that I write to with out_*, my variables are always in C style this_is_my_variables_name and I try to be as descriptive as possible of what the type is actually going to be used for.
One thing that I tend to pay particular attention to is when I want to pass an array of items into a function.
Just about everyone has used the size_t type - and everybody and their grandmothers know what the type means of course! The usual answers I get to ‘tell me what size_t is without Googling it’ is;
It is the parameter type for malloc to allocate memory! It is a platform dependent 32/64 bit unsigned integer type! It is what size_type in all the C++ std template hell is! (ok I made this one up - but fuck me the size_type lark really annoys me in the std code.) In general though the main assumption is that the size_t type is a platform agnostic way to represent any potential size of memory you could allocate or use.
So I previously installed Jenkins on my Raspberry Pi 2, and ran my first job through Jenkins. The final obvious step was to get another build node to connect to my Jenkins server so that workload can be offloaded from the Raspberry Pi 2 to another device.
The lovely folks over at Imagination Technologies sent me a MIPS Creator CI20 board a while back, and this seemed like the perfect node to add to my new Jenkins build farm!
So in my last post Installing Jenkins on Raspberry Pi 2 I took us through the steps it took me to get a Jenkins server running on my Raspberry Pi 2 - but I didn’t actually run any jobs on the Raspberry Pi 2! Time to rectify.
So I decided to build doboz - a really awesome little compression/decompression library written by Attila Áfra. I first forked it from HG -> Git, and fired it up onto my GitHub here.