Xin Wang

It seems that `char` in ACK's Pascal is 0-127, after I change `ordmaxchar` in `pcom.p` from `255` to `127`, the previous example compiles and runs correctly.

I think the character range is set by [type.c#L97](https://github.com/davidgiven/ack/blob/fd83b09c587b4a2d92102cc4f734b12087d6cb25/lang/pc/comp/type.c#L97), can not figure out why 7 bits characters is used instead of 8 bits.

For the set size, according to code in P5, I have checked that 256-bit is enough to compile it. The char > 127 is used by `pcom.pas`, which is used...

When trying to compile previous UTF-8 example, following error occurred: ``` "hello.p", line 4: newline in string "hello.p", line 9: newline in string "hello.p", line 9: , missing before string...

It seems that it's caused by old version of Bison (2.7 in CentOS 7), which do not include macro definitions for those constants (only enum definition is included), but `util/ncgg/cvtkeywords`...

Complied successfully after I change `bison` to `byacc`, I'll close this issue.

`lang/pc/libpc/READ_ME` also mentioned this problem. But this file is quite old, it maybe out of time.

I think that ISO 7185 does not specify module system, which is added in ISO 10206, both can be found at [here](http://www.pascal-central.com/standards.html).

With the fix in #44, compliation in FreeBSD can proceed further, but still failed with following error: ``` plat/linux68k/include+pkg lang/b/lib+lib_linux68k/init opt2: error on line 0: wrong input file /tmp/ack-build/staging/bin/ack: /tmp/ack-build/staging/lib/ack/em_opt2...

Hi @adimetrius, I tested it on Windows. I think it is "wrong" because current behaviour is not consistant with other applications, e.g. Notepad, Edge. It will be effected when I...