Support the use of volatile

[seba-eng]

the keyword volatile doesn't seem to work which makes things like benchmarking quite difficult.
minimal example:
#include <FixedPoints.h>
#include <FixedPointsCommon.h>

void setup() {
volatile SFixed<7, 8> f1, f2, f3;
f3=f1+f2;
}

void loop() {
}

this produces the error:

no match for 'operator+' (operand types are 'volatile SFixed<7u, 8u>' and 'volatile SFixed<7u, 8u>')

Or am I just doing it wrong?

[Pharap]

I hadn't expected anyone to need volatile versions.
Usually volatile is used for multi-threading, interrupts or special IO registers.

It should be easy enough to add volatile versions of the free functions, e.g.

template< unsigned Integer, unsigned Fraction >
constexpr SFixed<Integer, Fraction> operator +(const volatile SFixed<Integer, Fraction> & left, const volatile SFixed<Integer, Fraction> & right)
{
	using InternalType = typename SFixed<Integer, Fraction>::InternalType;
	return SFixed<Integer, Fraction>::fromInternal(static_cast<InternalType>(left.getInternal() + right.getInternal()));
}

But I don't know when I'll get chance to add them myself,
a lot of my time is currently taken up with other things.

[teuthid]

volatile is strongly neccesary if a given variable can be modified from the main program and from the interrupt(s) - quite a common phenomenon in programming for Arduino