FMSLogo Code

Fix bug #515; PORTWRITEARRAY now throws a "doesn't like input" error for its second input.

The motivation for this change is that PORTWRITEARRAY used to show a message which incorrectly referred to the first input when given a non-array second input. I could have instead corrected the text, but that would have left the non-English translations incorrect. This fix makes PORTWRITEARRAY act more like a typical FMSLogo procedure, throwing an error instead of displaying a dialog box that cannot be interacted with programmatically.

Since, after showing the dialog box with the incorrect message, PORTWRITEARRAY used to throw a "Stopping..." error, changing this to throwing a "Doesn't like input" error has negligable risk to backward compatibility.

Update the documentation for PORTWRITECHAR to match the implementation.
Specifically, PORTWRITECHAR ouptuts -1 on error, not 0.

Fix the documentation for PORTREADCHAR to match the implementation.
Specifically, PORTREADCHAR outputs negative integers when the bytes
read have their high bit set.

Fix a small, but significant error in the Spanish documentation for PORTREADARRAY and PORTREADCHAR.
The data is return as integers from -128 to 127, not -127 to 128.

Fix the documentation for PORTREADARRAY to match the implementation.
Bytes are read (not characters) and they are stored as integers from -128 to 127.

Correct places in the documentation where PORTREADARRAY is referred to as PORTMODE.

Fix the documentation of PORTWRITEARRAY to match the implementation.
This procedure outputs 1 on success, not the number of bytes written.
(At one time MSWLogo running on Windows 3.1 might have output the
number of bytes written, but it hasn't ever done that on 32-bit Windows)

Fix awkward wording "count many bytes" -> "count bytes"

Extend the tests for PORTWRITEARRAY and PORTWRITECHAR to additionally test the OUTPUT from these procedures.

Add manual regression tests for PORTREADARRAY.