On Thu, Mar 9, 2017 at 3:04 PM, Jay Kreibich <j...@kreibi.ch> wrote: > The main downside is that SQLite builds on a ton of platforms, including > embedded devices. In some cases, those platforms don’t even support > floating point numbers, never mind high-level math functions. It would add > a mess of new #defs. >
As Ryan already mentioned, embedded devices already disable large parts of the code, some even remove floating-points support, so a fortiori double-based math functions are out-of-scope. And it doesn't need to be a bunch of #def, 1 or 2 would be plenty. > There used to be a standard math extension that brought in a large number > of statistical math functions in a consistent way. I’m not sure what ever > happened to it, but that seems like a much better approach. > I'm not asking for a large number of stats functions. But the 1 or 2 dozens we all know and use. There's min(), max(), sum() and avg() and was really surprised not to see stddev() for example. --DD _______________________________________________ sqlite-users mailing list sqlite-users@mailinglists.sqlite.org http://mailinglists.sqlite.org/cgi-bin/mailman/listinfo/sqlite-users
