🚀 go-pugleaf

We are using the same compiler rather extensively.  We too have found
several bugs, but the most annoying ones are in the binary compiler
itself, so we cannot fix them:

TRUNC function generates incorrect assembly code

The name of a file containing the source code for a program cannot start
with a digit:  the compiler dies immediately.

If a source file has a syntax error in it, AND a line with > 132 chars,
the compiler dies before error messages are printed.  It can handle
lines > 132 chars as long as there are no syntax errors.

An exported ARRAY OF CHAR that is not 0-indexed is treated as
0-indexed when imported by a client module.

There are some other errors in the Libraries (not using MODLIB environment
variable as advertised, not setting "Done" in FileSystem.ReadRecord, ...,
but these can be fixed since we have the source for them.  What bugs
have you found, and how have you fixed them?  I would also like to modify
it to recognize the revised form of the language.  AT&T tells me that they
will post bug fixes and distribute source some time in the future through u3g,
the University System V Unix Users Group (mostly donation recipients).
in the mean time, we live with it.  I have written a manual page and a more
extensive user's guide.  Let me know if you want a copy.
______________________________________
Harvard Townsend, Systems Manager
Dept. of Computing & Information Sciences
Kansas State University, Manhattan, KS 66506   (913)532-6350
CSNET:  harv@kansas-state -or- harv@ksu.edu
BITNET: harv@ksuvax1.bitnet -or- harv%ksuvax1.bitnet@WISCVM.WISC.EDU
UUCP:   ihnp4!wnuxa!ksuvax1!harv
AT&T Mail: attmail!htownsend