Про сканер (если встроенного механизма комментариев или чего ещё -- мало) и вообще про "прерогативу Автора компилятора", Coco-Report.ps (подчёркивание моё)> -- Hanspeter Mo"ssenbo"ck писал(а):
> The scanner generated by Coco/R is optimized, but it is implemented as a deterministic finite automaton, which introduces some overhead. A manual implementation of the scanner is slightly more efficient.  This can be done by declaring all terminal symbols (including literals) as tokens but without defining their structure by an EBNF expression, e.g., If a named token is declared without structure, no scanner is generated...Using a generator usually increases productivity while at the same time flexibility is decreased. There are always special cases that can be handled more efficiently in a hand-written implementation.  Coco/R generates the scanner and the parser from source texts (so-called frames) stored under the names Scanner.FRM and Parser.FRM. It does so by inserting grammar-specific parts into these frames. The programmer may edit the frames and may therefore change any of the internally used algorithms. For example, he can Implement a different buffering scheme for input characters...