get a leaf value. More...

Detailed Description

get a leaf value.

Note: I don't think we should support CompositeValue, ArrayValue, and other possible future multi-value containers. I think we should only support "leaf" types - Primitive, String, Pointer, Enum And leave it up to other algorithms to find this types This is already what J_Checkpoint agent does However, if we switch to another format of checkpoint, like json or xml, which would lend itself to reconstructing entire objects rather than just leaves. This might be annoying if we decide to consolidate arrays or something idk maybe not It's simple enough to move the functionality here, it's probably better to keep the support rather than drop that. Actually no. I think tying the 'Value' hierarchy directly to the 'DataTypes' hierarchy is a bad idea. I want to drop that. If we want to create whole values in the future, we can make another DataTypeAlgorithm for that. But this isn't what I want to do. I also really hate that we're dynamic casting all over the place But I don't see a way around it without ~really~ tying the Value and Type hierarchies together

Typedef Documentation