I am looking for a JavaScript library to work with very small (very large) complex numbers. I need things like pow(), sqrt(), etc. Best I could find is Math.js [1], but it doesn't have arbitrary precision functions for complex numbers. To illustrate my point, please see this JSFiddle [2].<p>If there is no such library - what is the best alternative?<p>a.) create such a library from scratch<p>b.) convert some Java, Python, or C/C++ library to JavaScript using pyjs or Emscripten<p>[1] http://mathjs.org/<p>[2] https://jsfiddle.net/95mxb0dL/12/
Though I'm sure you'd rather avoid it, you can inspect other bignum implementations and perform a port. Coming from a Java library, for example, the port would be relatively straightforward, as syntax and semantics will largely match.<p>The most unpleasant thing is that JS doesn't have native ints, so you'll have to either use some other type as backing storage, and/or clever type coercion trickery, like what you see in asm.js.<p>[1] apfloat: <a href="http://grepcode.com/snapshot/repo1.maven.org/maven2/org.apfloat/apfloat/1.8.2/" rel="nofollow">http://grepcode.com/snapshot/repo1.maven.org/maven2/org.apfl...</a><p>[2] JDK's BigDecimal: <a href="http://grepcode.com/file/repository.grepcode.com/java/root/jdk/openjdk/8u40-b25/java/math/BigDecimal.java#BigDecimal" rel="nofollow">http://grepcode.com/file/repository.grepcode.com/java/root/j...</a>
There are not many JS libraries in this space that have sane handling for complex numbers and arbitrary precision.<p>I'm not entirely sure, but perhaps NumericJS [1] would have what you're looking for?<p>[1] <a href="http://www.numericjs.com/documentation.html" rel="nofollow">http://www.numericjs.com/documentation.html</a>
We should write a library for that with webgl + GLSL backend for faster computation (It would be quite a hack: textures would be used to store data and communicate with JS, but everything would be much faster). We could also use WebCL but this thing does not seem to work with many browsers.
I had a look at your jsfiddle, and it looks to me that it's a bug in mathjs. I have the impression that mathjs doesn't parse well complex numbers (I can be wrong there), so why not spend 1 hour to try to fix that bug before considering alternatives?