I didn't say anything about classes. I have a lot of programs
that don't access the database, with a lot of complicated
business logic behind them. Since I *know* programmers will
only read external documentation if they can't hunt me down
(even if I've left the company), at least putting comments
in the code gives them some direction.
For example, in one program with tons of statistical
calculations, I explain the arguments for calling an
external program to use the Fisher's Exact test to
calculate a probability. I put in a comment explaining
what the arguments mean, in case they get it in their
head to change it. It took me what seemed like *forever*
to get it to work right the first time, and I'm
just trying to spare them the same pain. Otherwise,
they'd have to go find a statistician (like I did).
But you're right, if you're just reading through a database
table and doing something with the data, unless it's extraordinary,
no comments are required.
A toggle switch is a great idea, by the way. In my VB2005
code, if I want to put in a block of comments, I put them
in a Region, and then it can be closed and opened as needed.
Robin S.
-------------------------