Move to C++11

[SAnsell]

Ok I have had enough of coding in the past. I am now enabling c++11 within the code. I will be providing no support for compilers that don't support c++11. If you are using gcc, getMk will automatically now add -std=c++11 to your compile line -- all will be good. [if you are using Redhat and gcc-4.4 -- update to something sensible]

Therefore, ALL of C++11 is open to use, that includes move operators (&&), lambdas, ranged loops and initializes, to name a few.

Not allowed: indiscriminate use of auto effectively loses a significant fraction of our type safety and code intent. At least 90% of autos I see in other peoples code, should not have been used.... Do not use it just because you can't figure out the type, or can't be bother to type, writing code is not the bottleneck reading it afterwards is. [same is true for dectype].

Please let me know if that causes real problems, or if there are any parts of the c++11 standard that you think should be strongly managed or forbidden.

At some point [hopefully soon] I will cut through the code and update boost stuff to std stuff, e.g. multi_array / shared_ptr etc.