IBM Mainframe Assembler List <[email protected]> wrote on 02/24/2014 03:15:47 PM:
> From: zMan <[email protected]> > Here's a fun experiment. Find your favorite *IX person. Ask them why > case-sensitivity is A Good Thing. Report back here. > > I have yet to find one who has any real reason other than "because". I started in EAM in 1961. I started programming mainframes (EDP) in 1964, IBM mainframes in 1966, ASM in 1967. Now I work on IT. Over the years I have worked in scientific programming, text processing and typesetting, system level programming and now applications programming. I wrote a utility that allowed the entry of u/l text w/o over-punching. Over punching on the old 3270 was difficult. I wrote a utility that allowed the conversion of UC files to u/l with field by field exception dictionaries. It helped service client requests. Over the years my ability to handle visual clutter has decreased. I now program both HLASM & Cobol in camelCase. My brain finds it friendlier. I follow this list regularly. It seems that certain neuralgic issues are hard to get over. When you have to get a job done you do it. If you can, you make life easier for yourself. I would find it painful where there are systems that find CAMELCASE camelCase and CamelCase to be different. But if I had to deal with that I think I would write a program to find and flag such instances. And to the extent possible facepalm anyone who did such things. So it goes. - grumpy ugly old white man ----------------------------------------- The information contained in this communication (including any attachments hereto) is confidential and is intended solely for the personal and confidential use of the individual or entity to whom it is addressed. If the reader of this message is not the intended recipient or an agent responsible for delivering it to the intended recipient, you are hereby notified that you have received this communication in error and that any review, dissemination, copying, or unauthorized use of this information, or the taking of any action in reliance on the contents of this information is strictly prohibited. If you have received this communication in error, please notify us immediately by e-mail, and delete the original message. Thank you
