No good reason. Way back in the day they were all Points, and then the fracturing began to support complex.
-Ben On Jun 12, 2012, at 5:14 PM, "Roy Stogner" <royst...@ices.utexas.edu> wrote: > > In today's episode of "let's nitpick Ben's 9 year old design > decisions", we ask: > > Does anyone recall exactly what the point was of the TypeVector vs > VectorValue distinction? I blindly copied it when creating TypeTensor > and TensorValue, but looking over the code again I don't see any > reason not to just simplify it away: we could add that > one-complex-from-two-reals constructor to the base class, then if > desired replace the VectorValue class with a typedef for backwards > compatibility. Most people already use the Gradient, RealGradient, > etc. typedefs, and for the others we could stick a cpp "#warning > deprecated" into vector_value.h and then get rid of it entirely in > a few years. > --- > Roy ------------------------------------------------------------------------------ Live Security Virtual Conference Exclusive live event will cover all the ways today's security and threat landscape has changed and how IT managers can respond. Discussions will include endpoint security, mobile security and the latest in malware threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/ _______________________________________________ Libmesh-devel mailing list Libmesh-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/libmesh-devel
