Oh, so. Thanks.
I'm used to get "google first" answers to technical questions - but it seems that Google starts to be a linguistic authority, too... :-)

Btw. while there was and will be much said on commenting practices - and Erik has very good points on it - there are situations, when one has to figure out the exact whereabouts of a program/routine without the comments - and not only when one "inherits" maintenance of badly or barely commented programs, but also when "proofreading" a program/routine, where the comments might mislead the "proofreader" to the way the programmer thought it rather than the way it works. Also some certification authorities while requiring general outline of a program, while checking it, they assume the comments may be misleading.

So I thought it can be an interesting idea for an another type of challenge to present an uncommented routine and the task is to guess what does it do. What do you think? (I know Erik does not like the idea)

Jan Waclawek