Thou shalt have no other gods before the ANSI C standard 1531

YES!!! My apologies. I'm still trying to learn how write as well as you guys do.

Sure. But those comments will only mean something to a maintainer of the code. IOW, s-he has read the code. I don't hear about anybody teaching by using the OS listings as the textbook. And even if they did use listings, they would have to have each and every release of that OS so that the code can be compared and its evolution studied. The best we could do was ship the MCO (monitor Change Order) file with each release. It would have taken 3-4 manyears of dedicated digging to analyze why and how a particular routine (not even a module) changed over the years.

And all of this code evolution has to do with what did NOT work.

to ago two,

IOW, these profs sold their project notebook that was prettied up for public consumption. Most businesses view their project notebooks as company confidential or, if it's a government, a high security clbuttification.

Now, how can profs teach what they can't learn about?

Note that I am no longer talking about the few instructors who deliberately mislead their students. I've moved on to dealing with the problem.

BAH

Subtract a hundred and four for e-mail.