LOLCODE docs: implementation and testing pages (items 21-25) #161

Found while marking the LOLCODE assignment (Fall 2026, 36 submissions). The quoted text is from lolcode/ and info/ on master.

Each item can be fixed and ticked off separately.

• 21. Generated parser

  index.rst says the ANTLR grammar "only needs lexical rules" and that writing parser rules may help. Two students used the generated parser; many left parser rules that still generate an unused LolCodeParser.

  Proposed fix: "Your submission must not use an ANTLR-generated parser; use lexer grammar."

• 22. Test directives for a language without // comments

  info/dragon_runner.rst says directives use "the language's line-comment syntax (//)"; LOLCODE needs "commentPrefix": "BTW", which is not documented. Students used BTW CHECK:, BTW //CHECK:, and bare //CHECK: (with a non-spec // lexer rule).

  Proposed fix: a LOLCODE example config and test file on the dragon-runner page.

• 23. Package name

  info/testing.rst says the package is named for the CCID ("if your SID is 1660000, then ... tests/testfiles/160000", which also has a typo); the template pre-commit hook derives 415-lolcode-<user> from the repo name. Three students committed both.

  Proposed fix: one convention in both places.

• 24. Assertion examples are from another language

  impl/assertions.rst uses C-like examples (int i = -1;, int i = 1 / 0;).

  Proposed fix: LOLCODE examples.

• 25. "Seven types of statements" omits some

  spec/statements.rst lists declaration, assignment, cast, I/O, loop, conditional, case; GTFO and the bare-expression statement used by O RLY?/WTF? are not listed.