: Yeah, I've had the same idea... typing of the functions. I think : we'll get to that sooner or later, but I'm not sure it's something we : can do for 1.4, and it would seem to cause a proliferation of classes : (or switch statements at every level?).
i don't see why it would cause either ... at every level the classes should still be able to do whatever it is they do for each of the supported datatypes (just like they do now) only the top level (FunctionQuery or anybody else directly accessing a ValueSource) would need a switch statement, and even that's only if they wanted to support the highest precision possible -- if they don't care, they can just call getFloatValue and it will still keep on working. : : But perhaps we should default to double precision math, even when the : operands are floats? Seems like it would help prevent rounding : errors. probably ... anybody know how the overhead of int=>double & float => double compare to int=>float & double=>float ? -Hoss
