what I always wondered about: Why does 'typedef' not create ... a type?
The compiler acts as if I had just compared int. no error, no warning at highest warning level, although it would be really easy to do and help to avoid a whole class of programming errors. A try to pass mPolygon.getArea_squaremeters() to setPriceOfIceCream_dollars() could be found at compile time and programmers could get rid of putting units on symbols.Code:
typedef int T1;
typedef int T2;
t1 == t2;
Is this maybe going to be fixed by new standard?