Path: utzoo!news-server.csri.toronto.edu!rutgers!sun-barr!lll-winken!sol.ctr.columbia.edu!samsung!usc!cs.utexas.edu!sdd.hp.com!caen!hellgate.utah.edu!dog.ee.lbl.gov!ucbvax!USCMVSA.BITNET!LDW From: LDW@USCMVSA.BITNET (Leonard D Woren) Newsgroups: comp.lang.asm370 Subject: Re: programming style Message-ID: <9103090641.AA07447@ucbvax.Berkeley.EDU> Date: 9 Mar 91 06:39:00 GMT Sender: daemon@ucbvax.BERKELEY.EDU Reply-To: IBM 370 Assembly Programming Discussion List Distribution: inet Organization: The Internet Lines: 16 > The fact is, if I have to look at the code closely enough to need to > know the structuring, I'm probably not going to pay much attention to > the comments at all. It is what is to the left of the comments that > really tells you what is happening, and when push comes to shove that is > what you must rely on. Yep. I was once reading JES2 source, trying to determine whether something was a feature or a bug. I came to one line where the comment seemed to conflict with the instruction. After staring at it for an hour, I called the support center. The level 2 person checked into it and discovered that the comment was backwards. They wouldn't take an APAR to fix the comment, but said they'd "leave a note on the board for someone to fix that comment the next time that area was touched." Sigh. /Leonard