Practically speaking, no. Terse J code is good at encapsulating a process but does not place it in a context like a comment might: it doesn't give you an idea of implicit limitations or purpose of the process.
That said, a single-line comment is probably all you need for most J programs. On Mon, May 19, 2014 at 2:38 PM, Eldon Eller <[email protected]> wrote: > Doesn't a paragraph of explanation vitiate the terseness of J? > > > On 05/19/2014 11:21 AM, Brian Schott wrote: > >> Below is an example of monadic Note. >> I have no sense of how dyadic Note would help. >> >> Note 'How Note works' >> Note works likes this. >> Enter any text for a comment >> and when you are done, just >> type a right paren on a line >> by itself. >> ) >> >> >> On Mon, May 19, 2014 at 11:33 AM, Don Guinn <[email protected]> wrote: >> >> Don't forget about "Note". I like to use the right argument as a title >>> or a >>> one line description. Then put the detailed description below. This gives >>> the possibility to provide self-documenting by redefining "Note" to >>> extract >>> information for help. And we still have the left argument to play with. >>> >>> >>> -- >>> >> (B=) >> ---------------------------------------------------------------------- >> For information about J forums see http://www.jsoftware.com/forums.htm >> >> > ---------------------------------------------------------------------- > For information about J forums see http://www.jsoftware.com/forums.htm > -- Devon McCormick, CFA ---------------------------------------------------------------------- For information about J forums see http://www.jsoftware.com/forums.htm
