As an aside, in the last century the leading PC C++ compiler vendor was not Microsoft but Borland. One day they got too big for their boots and issued a proclamation which dictated that all users of their IDE must code in their prescribed style - which included suffixing the "*" to the type instead of K&R's prefixing "*" to the variable name. It was at this point that I stopped using Borland. For the sake of consistency, I can't resist also applying the K&R style to references too; although I'm clearly flying in the face of convention from the majority of code examples that I see in books and on-line.

No, I've got no public code - it's all proprietary (but more out of laziness than anything). Though I really aught to publish my general-purpose template driver library for the ARM-based Atmel SAM series of microcontrollers. One might argue that template programming is sometimes inefficient code size-wise, but microcontrollers often have a generous amount of on-board flash (and really very little in the way of RAM) so it doesn't matter. Also, as we can make the compiler produce code for each individual module, say a timer, we don't need to maintain differences between one timer and another e.g. register addresses, I/O pin assignments, differences in functional ability etc in precious RAM - it can all get hard coded with added performance benefits. If you're interested, I recommend "Real-Time C++ - Efficient Object-Orientated and Template Microcontroller Programming" by Chris Kormanyos.

Hear, hear. I got back into programming microcontrollers after a 15 year break and was shocked to see that frameworks and libraries had not really evolved in all that time one jot. Using a bit of C++ template programming to create drivers for on-board hardware modules made everything really sweet - and fast too. Sorry, total departure from the original topic. I'll crawl back into my hole...