FMSLogo Code

Remove an extra space from a comment

Rename ecma_* functions:
ecma_set -> vbar_set
ecma_clear -> vbar_clear
ecma_get -> is_vbarred

I think "ecma" was to indicate this shifting was to support Western European characters, although even then, as a prefix it doesn't make sense because it shifted special characters to ASCII control characters. Now that FMSLogo supports Unicode, the using the "ecma" prefix is even sillier.

"vbar" better describes what these functions are doing. And "is_vbarred" was preferred to "vbar_get" because the function is a predicate and doesn't "get" anything.

Refactoring: Change g_SpecialCharacters to an array instead of string literal
This removes the need to subtract one to remove the NUL terminator.
It also removes the temptation of using wscchr(), which includes the NUL.

Update a bug number referenced in a comment.
When Dice bought SourceForge, they re-numbered all of the bugs.

Cleanup: Remove unneeded LOCAL in READWORDTEST.UICANCEL
This was probably a copy&paste error.

Fix a regression where NUL was backslashed.
This is a regression from UCBLogo, but was made worse by the Unicode changes in that NUL was backslashed but not unbackslashed.

Fix bug #542 - typo in documentation for ` (backtick)
:, was documented as "quote comma" instead of "colon comma".

Improve test logging in WORKSPACETEST.ARRAYWITHBINARYDATA.ALLVALUES
(Now the value of REPCOUNT is logged, instead of "REPCOUNT").

Update WORKSPACETEST for the Unicode FMSLogo
- Fix an off-by-one error in WORKSPACETEST.WORDWITHBINARYDATA.ALLVALUES that resulted in 256 false-positive failures.
- Use SIMPLEREPORTTEST, where appropriate. SIMPLEREPORTTEST has been updated to no longer write NUL characters and so is safe to use.
- Capitalize procedure names.

At this point, there is only one failure, which is that a NUL byte is not saved/loaded correctly.

Clarify why SIMPLEREPORTTEST.CHECKRESULT sets :caseignoredp
(Using EQUALP? made the comment look like a question, not an explanation)