The call of the DoMathsSub routine from DoMaths_AsDouble instead of calculating directly in this routine makes the differenche.
Yes, because the called Sub doesn't do much work so the call overhead is high. Hence the emphasis on the help in doing a significant amount of work in a called Sub or or inlining what would otherwise be small Subs.
__________________
Sorry, but I don't answer questions by PM or email.
Please post your queries in the forum.
Version 1.4 now copes with "=" and "<>" in conditional expressions, previously they threw a cast exception. The other comparison operators worked fine as they always assume numeric quantities but as "=" and "<>" can also be used on strings the optimising compiler treats them differently and I hadn't taken this into account .
__________________
Sorry, but I don't answer questions by PM or email.
Please post your queries in the forum.
I didn't deliberately design it to do so but it seems that version 1.4 works with Single, Int32 and Int64 arrays as well as Doubles which could be useful to save memory with large data sets.
Post the code here if you try it and it doesn't work and I'll take a look.
__________________
Sorry, but I don't answer questions by PM or email.
Please post your queries in the forum.