FMSLogo Code

Update the "banned words" to include "i.e." and "e.g.".
Update the banner comment .

Fix that the range of characters used by ASCII, RAWASCII, and CHAR is from 0-255, not 0-127. Also add a "See Also" section.

Restructure the COPYDEF tests to look more like my other tests.

I also switched in some tests for bug #1454113 which no longer crash. I added a new test that uses COPYDEF in a recursive, but not tail-recursive call, which still crashes due to bug #1454113. This test case is currently commented-out.

Also, fix a bug in EVALTEST.TAILRECURSIVECOUNT that made it always output 0. This bug led to two false-positives per test pass.

Fix a bug in EVALTEST.TAILRECURSIVECOUNT that made it always output 0. This bug led to two false-positives per test pass.

Restructure the COPYDEF tests to look more like my other tests.

I also switched in some tests for bug #1454113 which no longer crash. I added a new test that uses COPYDEF in a recursive, but not tail-recursive call, which still crashes due to bug #1454113. This test case is currently commented-out.

Add a mitigation for bug #1454113; Using COPYDEF of OUTPUT can crash.

The fix was copied in from UCBLogo, but that fix leaks memory. The problem is that the code doesn't "re-treeify" a body node if the definition of a function changes in mid-execution, which could crash if the definition changed in a significant way for tree-ification (such going from undefined to defined, or changing the number of inputs).

UCBLogo "leaks" the tree-ificiation of the procedure, which is not a problem for UCBLogo, because it has true garbage collection. But this results in a very significant memory leak for FMSLogo. My stop-gap fix for this memory leak is to untree-ify the procedure after it is executed. Unfortunately, this means that the original bug still exists for functions that are tree-recursive (non-tail recursive) because once the inner call exits, the outer call becomes untree-ified and can no longer handle having a procedure change.

Since the current change reduces the scope of the bug, I am checking it in. I'm not sure what the final fix will be-it may either be a reference count on the tree-ification or simply to keep the tree-ification around for the lifetime of the procedure.

Add benchmarks for running tail-recursive and non-tail recursive procedures.

Add a regression test for bug #1552426, which crashes.

Add some tests that are intended to test the evaluator.

Add function comment for parser_iterate().