We should stick to 80-character lines of text, everywhere.

Grigore


________________________________
From: traiansf [notifications@github.com]
Sent: Tuesday, March 04, 2014 3:10 AM
To: kframework/k
Subject: Re: [k] Added many documentation comments; added a "nodoc" tag. (#264)


In include/builtins/k-reference.k:

> +This reference manual is designed to provide answers to questions that tend to
> +arise over the course of using \K. In it, several sections are devoted to
> +features of \K and \K usage, while the remaining sections are devoted to
> +providing documentation on \K's builtin classes and structures. The document is
> +entirely searchable; ctrl+f is probably the most straightforward method of
> +trying to find relevant information. Links to the builtin modules are provided
> +at the beginning of the document. This manual is a work in progress; if there's a
> +question whose solution you were unable to find in this manual, please send an
> +email to (TODO: get email address) detailing the nature of the question and a
> +suggestion as to where it might best be placed.
> +*/
> +
> +
> +
> +/*@ \section{Builtin Literals}
> +K has predefined the lexer rules for the most common syntactic categories that are directly accessible through subsorting:


maybe shorter line?

—
Reply to this email directly or view it on GitHub<https://github.com/kframework/k/pull/264/files#r10247241>.