Syntax Cleanup

-Comma separated object properties
-Explicit semicolons and Braces
-Stricter equality checks where appropriate
Fewer Globals

Var declarations to prevent internal variables from leaking out of their functions
Real, Catchable Errors
Fix transpose, simpsonRecursive

Transpose wasn't returning anything and was overwriting the data as it attempted to move it. My new implementation probably isn't that fast, but it works.

SimpsonRecursive, I think, just had a typo.
Fixed Identity function

-Zeroes needed to be set explicitly
-Typos
Merge pull request #4 from ethanresnick/master

Same as last pull request (my bad; merged my changes into master on my fork)
Update README.md
fix indentation
Merge branch 'master' of github.com:sjkaliski/numeric.ly
cleaning it up
restructuring for npm
more organizing
More robust, but still backwards-compatible, evaluate()

Using Math and string function names in evaluate() will prove limiting, imo, mainly because it means custom functions (not part of Math) can't be evaluated, which is a big loss. For instance, it means there's no way for me to pass in my own function and find its limit. Also eval() is slow and with isn't allowed in ES5 strict.

This version allows (really prefers) any function to be passed in as a function object, but uses a type check to support the earlier API.

If possible though, I'd probably drop that API all together.
Merge pull request #5 from ethanresnick/patch-1

More robust, but still backwards-compatible, evaluate()
add factorial using memoization
Merge branch 'master' of github.com:sjkaliski/numeric.ly
added prime factorization, although not a great implementation yet, will likely switch to rho algorithm
rewriting using classes, added basic tests
Update README.md
modified implementations for few numeric evaluations