I'm missing something--what's wrong with the comments being mixed case? Other than them getting folded to uppercase, maybe, when you make changes? But how is that such a problem?
Almost 40 years ago I had an XEDIT mod, "AUTOCASE". When that was set and you updated a line, if the line was all lowercase, it would uppercase it; if it was mixed, it left it alone. That let you write assembler by typing the label/instruction, hitting ENTER, then <tab> and enter the comment in mixed case. Worked really well. Yes, I'm 100% sure that I've read studies that mixed case is easier to read. -----Original Message----- From: IBM Mainframe Assembler List <ASSEMBLER-LIST@LISTSERV.UGA.EDU> On Behalf Of Peter Relson Sent: Wednesday, August 27, 2025 8:28 AM To: ASSEMBLER-LIST@LISTSERV.UGA.EDU Subject: Re: Is HLASM efficient WAS: Telum and SpyreWAS: Vector instruction performance <snip>My personal pet peeve is files where the non-comment content *must* be in upper case, but the IBM samples are provided with mixed case comments. Hello, JES2 initialization members.</snip> Isn't it true (or is this no longer a "thing") that mixed case text is "easier" to read and has better comprehension than all upper-case or all lower-case? That's what I learned long ago, but I'll admit that I never read a "real" study on the subject. Anyway, if it's true, then doesn't it make sense to have mixed-case comments (which are meant to be "read") even if the command requires upper-case? Peter Relson
