Re: An attack on a mint

ja, i'd suggest that if you want to get a point P across, then say
point P in the comments, rather than something
related-but-not-exactly-P.

if writing P out is too long and complicated then you could do any/all of:

(a) put a url in the comments that links to a wiki explaining it.
(b) have unit tests which show when things are broken, and which are
given names like "testOrderOfOperations()" etc.
(c) have the comment say some standard marker along the lines of
"TODO" or "FIXME" which is maybe like "DO NOT ALTER" with the
convention that that means the programmer has to triple-check any
changes to that code ;-).

$0.02