Cal3Unified not correct Value

@richardroberts and I figured out that Cal3Unified is wrong. Look in DerivedValue and you'll see that it implements the virtual functions defined in Value, and in implementing them, calls the functions in DERIVED (which would be Cal3_S2 and not Cal3Unified). So, any code that relies on calling the virtual functions in Value, which includes copying, retracting, localCoordinatesing, etc, a Values object, will turn all Cal3Unified objects into Cal3_S2 objects.

@richardroberts also said:

June 19, 2014 at 12:57 PM
Hi Frank, I spent a bit of time just now trying to see how to do this and I don't
think there's a good way to do it while using DerivedValue.  DerivedValue fills in 
boilerplate code required for creating a class that derives from Value, but it wasn't 
written with further derived classes in mind.  You may still do it by deriving directly 
from Value and then implementing the functions that DerivedValue implements, e.g.
writing this boilerplate code in the derived classes.  Or by rethinking DerivedValue 
so that it can work with an inheritance chain.

I am thinking this could be solved by having both Cal3Unified and Cal3DS2 be subclasses of DerivedValue and Cal3DS2_Base, which is not a value.

Comments (9)