Re: CamelCase (was: ASSEMBLER-LIST Digest ...)
On 1 March 2014 00:12, Robert A. Rosenberg a...@rarpsl.com wrote: Making STUFF stuff Stuff sTuff ... have different meanings is not as fault-tolerant as it could be. OTOH: Polish and polish ARE not the same. Telling someone in the army to You should Polish your shoes so you will pass inspection or claiming I am a polish citizen are both bad uses of the string p-o-l-i-s-h since the wrong case of the letter P/p makes the meaning of that string in the statements incorrect. This oft used example is barely relevant in our context. If anyone encounters YOU SHOULD POLISH YOUR SHOES SO YOU WILL PASS INSPECTION or i am a polish citizen they will understand without the slightest hint of ambiguity. If they think anything's wrong, it will that someone's keyboard skills are weak - not that polishing compounds can affect citizenship, or citizens are applied to shoes to shine them. In the context of identifiers in programming languages, there is in my view only a weak and sometimes entirely spurious argument in favour of sensitivity to case. Tony H.
Re: CamelCase (was: ASSEMBLER-LIST Digest ...)
I think this discussion needs to distinguish clearly between case-sensitive (treating caps and lower case the same) and case-insensitive (treating the upper and lower case of the same character as different). Mixed-case could mean either, and is therefore unclear. IMHO, case-insensitivity is not human-friendly. I can't think of any reason to use it, but no doubt someone has, On Fri, Feb 28, 2014 at 9:52 AM, Paul Gilmartin paulgboul...@aim.comwrote: On 2014-02-25, at 10:00, John Walker wrote: So, to respond to the one comment, it was ok for the Science guys to want mixed case things because that was what they were used to. Ok, I can buy that. Same rationale can be applied to the C programmers. Now, let's be fair, using the very same reasoning, I can then justify MY perception that mixed case shouldn't be used on the mainframe, because I am used to it. Now, if you say they can justify their actions out of their preferrences and I can NOT do the same thing, then you surely can see how that is not fair for everyone, right? Let's see. The monocase enthusiasts have JCL as they like it. The mixed case enthuiasts have C as they like it. All within the z/OS environment. Something for everyone. Sounds like a compromise; everyone should be happy. You sound bitter; intolerant. Would you stop the science guys at the border because they speak a different language? Why did you write your messave in mixed case? It's probably OK as long as you didn't compose it on a mainframe. -- gil -- OREXXMan
Re: CamelCase (was: ASSEMBLER-LIST Digest ...)
IBM Mainframe Assembler List ASSEMBLER-LIST@LISTSERV.UGA.EDU wrote on 02/28/2014 11:18:33 AM: From: Hobart Spitz orexx...@gmail.com I think this discussion needs to distinguish clearly between case-sensitive (treating caps and lower case the same) and case-insensitive (treating the upper and lower case of the same character as different). Mixed-case could mean either, and is therefore unclear. IMHO, case-insensitivity is not human-friendly. I can't think of any reason to use it, but no doubt someone has, In human language based communication with other humans, case-sensitivity is meaningful and helpful. In any communication with automatons (except data entry), case-insensitivity is more human-friendly and can be easily tolerated by the machine(s). Making STUFF stuff Stuff sTuff ... have different meanings is not as fault-tolerant as it could be. ... Efforts and courage are not enough without purpose and direction. - John F. Kennedy Fasten your seat belts, it's going to be a bumpy ride. - Bette Davis (as character Margo Channing) _All About Eve_1950 Our greatest danger in life is in permitting the urgent things to crowd out the important. - Charles E. Hummel Quidquid latine dictum sit, altum viditur. - 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
Re: CamelCase (was: ASSEMBLER-LIST Digest ...)
I should be be on John Walker's side if 'z/OS' were telling him that he may no longer write his routines in headlines. As it is, what he appears to be saying is that I must write mine in headlines too; and I am unsympathetic, even hostile to that notion. He is and should be free to continue what he has always done, but not to impose his views upon others. There is, however, a larger issue here. Traditional all-majuscules source programs have two essential characteristics: They reflect now irrelevant, circa-1956 hardware technology; and they have a strong, all the stronger for being implicit and unexamined, anglophone bias. Consider the lines from José Camargo Caïn a été humilié par Dieu, et il tue son frère parce qu'il est dans l'incapacité de tuer Dieu. Rendered in majuscules without disacritical marks as CAIN A ETE HUMILIE PAR DIEU, ET IL TUE SON FRERE PARCE QU'IL EST DANS L'INCAPACITE DE TUER DIEU. it is, for a francophone, defaced. I look forward to the time when we shall be able to write source programs in mixed-case Unicode. Bertrand Russell once observed that if professional football (soccer) players came to be oppressed, he would of course come to their defense, diligently if not with great zeal. My view of Mr. Walker's problem is much the same. John Gilmore, Ashland, MA 01721 - USA
Re: CamelCase (was: ASSEMBLER-LIST Digest ...)
At 11:18 -0500 on 02/28/2014, Hobart Spitz wrote about Re: CamelCase (was: ASSEMBLER-LIST Digest ...): I think this discussion needs to distinguish clearly between case-sensitive (treating caps and lower case the same) and case-insensitive (treating the upper and lower case of the same character as different). You have your definitions backwards. If I am case-sensitive I care about the case and thus see A as different from a. If I am case-insensitive I do see A and a as the same character (and thus the same string of characters is the same no matter what CamelCase glyphs are used).
Re: CamelCase (was: ASSEMBLER-LIST Digest ...)
At 11:28 -0500 on 02/28/2014, Kirk Talman wrote about Re: CamelCase (was: ASSEMBLER-LIST Digest ...): Making STUFF stuff Stuff sTuff ... have different meanings is not as fault-tolerant as it could be. OTOH: Polish and polish ARE not the same. Telling someone in the army to You should Polish your shoes so you will pass inspection or claiming I am a polish citizen are both bad uses of the string p-o-l-i-s-h since the wrong case of the letter P/p makes the meaning of that string in the statements incorrect.
