Function and operator name changes to the JavaScript version of MathPiper and the new building and testing systems.

[Ted Kosan]

I have already made so many changes to the JavaScript version of
MathPiper that I have decided to keep going and apply a number of the
name changes that are listed in
src/doc/yacas_to_mathpiper_function_name_changes.txt so I can test
them in the MathPiper classes I will be teaching this Fall. The most
radical of these changes involves having all predicate functions and
operators end with a ?, which is similar to what Scheme does.

Sherm (and anyone else who is interested),

You can start experimenting with the new build and testing system if
you would like in order to prepare for working on the factoring code.
For now you will need to edit the following string array which is on
line 441 of Build.java in order to enable the building of functions
which are currently in the "do not build" list:

String[] functionsNotToBuild = {"CForm",
"IsCFormable", "issues", "debug", "jFactorsPoly", "jasFactorsInt",
"xContent", "xFactor", "xFactors",
"xFactorsBinomial", "xFactorsResiduals", "xPrimitivePart", "html",
"odesolver",
"orthopoly", "openmath", "ManipEquations",
"Manipulate", "SolveSetEqns", "ControlChart", "GeoGebra",
"GeoGebraHistogram",
"GeoGebraPlot", "GeoGebraPoint", "ggbLine",
"HighschoolForm", "jas_test", "JFreeChartHistogram", "JavaAccess",
"RForm",
"xCheckSolution", "xSolve", "xSolvePoly",
"xSolveRational", "xSolveReduce", "xSolveSqrts", "xSolveSystem",
"xTerms",};

Here are instructions for building MathPiperJS and testing it:

//Build MathPiperJS:
ant build

//Get help on the new test suite command line switches:
java org.mathpiper.test.TestSuite -h
-s test,test,... (Run only some of the tests, the ones that are listed).)
-e test,test,... (Run all of the tests, except for the ones that are listed.)
-f <file name> (Specifies the name and path of the log file.)
-t (Include a stack trace when an exception is thrown.)
-p (Print each test just before it is evaluated.)

//Run the full test suite:
java org.mathpiper.test.TestSuite

//Run only some of the tests:
java org.mathpiper.test.TestSuite -s LaplaceTransform,Easter

Let me know if you run into problems.

Ted

[Nicky Nickell]

I was initially unable to build MathPiperJS. In 

src/org/mathpiper/interpreters/SynchronousInterpreter.java there was

an extra argument passed to the constructor of MathPiperParser

(it was only null), but once removed I was able to build without

problem and run the tests.

[Ted Kosan]

Nick wrote:

Thanks for catching this. I am in the process of modifying the parser
so that it can identify the locations where any functions or operators
are used in a script and I committed the extra null argument by
mistake.

Ted