I do have a reg class template which handles all bit manipulation and register access, but that is the only templates in use for my pic32mm. The code is easier to read/change/understand, and any cost is speed is worth it. It ends up being just fine on a pic32 which can handle pointers/objects with ease. The library includes implementations of conio.h functions that mimic Borland Turbo C++ to set video modes, display colored text, move the cursor, and so on. With the pic32mm (256K/32K), I started to use templates but then switched to 'normal' coding to keep things simple. You can also find a similar conio implementation in TK Chias IA-16 DOS port of the GNU C Compiler in the libi86 library of non-standard routines.

The advantage, and really the only good option on a limited flash micro like the tiny416 is you end up with small code and you don't get the compiler trying to use pointers all the time, which look sort of ugly on these 8bitters. h header files contains definition of some specific words e.g iostream.h contain defination of cout. output/low is on (4 instructions- pin mode and pin set to 'off') led.on() //a single 'sbi 1, 0' (set bit since pin is in invert mode) The disadvantage when you get into templates, is it 'infects' everything and you end up having to use templates quite often. h and conio.h are header files having extension of. The big advantage of the templates is you can end up with- PA0_OUTL_t led //sets pin mode.

I am also using c++ for a tiny416- where I use templates and it is mostly just a collection of headers. With only c++11 support, constexpr seems to end up limited (for constexpr functions anyway), unless you are a recursive coding guru. >It would be nice to use templates and constexpr to generate really fast, small code for handling the peripherals.

Conio library c++