Path: csiph.com!x330-a1.tempe.blueboxinc.net!usenet.pasdenom.info!news.albasani.net!eternal-september.org!feeder.eternal-september.org!.POSTED!not-for-mail From: Gene Wirchenko Newsgroups: comp.lang.java.programmer Subject: Re: CLI Java Glitch Date: Thu, 23 Jun 2011 14:32:26 -0700 Organization: A noiseless patient Spider Lines: 25 Message-ID: References: <4dffe2ea$0$57121$c30e37c6@exi-reader.telstra.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Injection-Info: mx04.eternal-september.org; posting-host="7Qrvczazr82YckO5XW8Vtw"; logging-data="8722"; mail-complaints-to="abuse@eternal-september.org"; posting-account="U2FsdGVkX19NDgMKizQwKrTk2X8SdEeGySibo3aeIc4=" X-Newsreader: Forte Agent 4.2/32.1118 Cancel-Lock: sha1:NBpAX1JJ0A5PmP268a9vgOKFd74= Xref: x330-a1.tempe.blueboxinc.net comp.lang.java.programmer:5601 On Thu, 23 Jun 2011 12:24:06 -0400, Michael Wojcik wrote: >Peter Duniho wrote: >> For better or worse, Java _is_ case-sensitive, which means >> that it definitely should be just as illegal for the user to specify >> "helloworld" as the class name when starting the program as it is for >> the programmer to specify "helloworld" as the class name when referring >> to it from code. > >Agreed. And "case-insensitive" becomes problematic when you move >outside European alphabets, which is another argument against it. (If >I name a class using Japanese katakana characters, should I be able to >invoke it using the corresponding hiragana characters? That would seem >pretty silly - but where do we draw the line?) Somewhere before the slippery slope? Just because it is difficult to implement something 100% does not mean that there is no benefit to going for the easy, say, 80%. [snip] Sincerely, Gene Wirchenko