HTTP/1.1 -1 Read error in cache disk data: SuccessContent-Type: text/tab-separated-values; charset="utf-8" Last-Modified: Sat, 22 Jan 2022 02:33:27 GMT Content-length: 1582 Connection: Close Proxy-Connection: Close X-Cache: HIT from web1.osuosl.org Server: ProxyTrack 0.5 (HTTrack 3.49.2) id summary reporter owner description type status priority milestone component version severity resolution keywords cc lang patch platform 1913 README issues ajs whiteknight "A mix of typographical and content issues. At revision: https://github.com/parrot/pirc/blob/c1310171310ddc47864b480a87322911fa7dc5b1/README.pod I see the following issues in the README: 1. ""README file for PIRC compiler"" should add ""the"" before ""PIRC"" 2. ""... PIR programmer, and flattens ..."" lose the comma 3. ""replacing the above statement by"" arguably ""with"" instead of ""by"" 4. The whole paragraph and example, "" In C one would write (ignoring the fact that $I0 and $I0 are not a valid C identifiers)"" can be replaced with ""The C<+=> operator in many C-like languages can be used in PIR to simplify this operation, and PIRC does this for you,"" which then blends into ""as if you had written:"" below. 5. ""Again, in C one would write (again ignoring"" redundant and cumbersome. How about ""The C-like convention here is the postfix C<++> or C the..."" 6. ""The directory compilers/pirc has a number of subdirectories"" Change this to ""The PIRC compiler source tree has a number of subdirectories"" 7. The ""Cygwin processable lexer spec"" section is only true at a given point in time. The date should be mentioned. Presumably, Cygwin will be updated in the future. 8. ""SEE ALSO"" section references several areas in the Parrot distribution, and should be noted as such. " todo closed minor 3.0 docs master low fixed README gci all s>