|
|
|
|
|
by randomdata
5000 days ago
|
|
Wouldn't that kind of information be better expressed in machine-human-readbale formats outside of the code that can be used to not only convey the information to the reader, but also verify that the description does as it says it does? I will agree that some of that information is worth writing down, but I'm not yet convinced a comment within the code is the right place for it. > These are extremely important in loosely typed languages where there is little indication as to what constitutes an acceptable argument. Isn't that just pushing language "flaws" into the comments, not unlike annotations are being used here? I'll grant you that it is pragmatic when faced with lack of tools, but the grandparent suggested annotation comments were a bad idea but comments were a great idea, which seems contradictory to me in light of this. |
|
Remember that comments and documentation are no substitute for proper testing that will expose usage errors. No amount of machine readable specification can prevent this, so it's often a waste of programmer time to produce.