Definition: comment
Source: WordNet (r) 1.7
comment
n 1: a statement that expresses a personal opinion or belief;
"from time to time she contributed a personal comment on
his account" [syn: remark]
2: a written explanation or criticism or illustration that is
added to a book or other textual material; "he wrote an
extended comment on the proposal" [syn: commentary]
3: a report (often malicious) about the behavior of other
people; "the divorce caused much gossip" [syn: gossip, scuttlebutt]
v 1: make or write comment to make a comment on [syn: notice, remark,
point out]
2: explain or interpret something
3: provide interlinear explanations for words or phrases [syn:
gloss]
Source: Webster's Revised Unabridged Dictionary (1913)
Comment \Com"ment\, v. t. To comment on. [Archaic.] --Fuller.
Comment \Com"ment\, n. [Cf. OF. comment.]
1. A remark, observation, or criticism; gossip; discourse;
talk.
Their lavish comment when her name was named.
--Tennyson.
2. A note or observation intended to explain, illustrate, or
criticise the meaning of a writing, book, etc.;
explanation; annotation; exposition.
All the volumes of philosophy, With all their
comments. --Prior.
Comment \Com"ment\ (?; 277), v. i. [imp. & p. p. Commented; p. pr. & vb. n. Commenting.] [F. commenter, L. commentari to meditate upon, explain, v. intens. of comminisci, commentus, to reflect upon, invent; com- + the root of meminisse to remember, mens mind. See Mind.] To make remarks, observations, or criticism; especially, to write notes on the works of an author, with a view to illustrate his meaning, or to explain particular passages; to write annotations; -- often followed by on or upon. A physician to comment on your malady. --Shak. Critics . . . proceed to comment on him. --Dryden. I must translate and comment. --Pope.
Source: The Free On-line Dictionary of Computing (2003-OCT-10)
comment <programming> (Or "remark") Explanatory text embedded in program source (or less often data) intended to help human readers understand it. Code completely without comments is often hard to read, but too heavily commented code isn't much better, especially if the comments are not kept up-to-date with changes to the code. Too much commenting may mean that the code is over-complicated. A good rule is to comment everything that needs it but write code that doesn't need much of it. A particularly irksome form of over-commenting explains exactly what each statement does, even when it is obvious to any reasonably competant programmer, e.g. /* Open the input file */ infd = open(input_file, O_RDONLY); (1998-04-28)
