On Wed, 22 Dec 2004 15:39:53 -0500, Ben Souther wrote:

>
>> This is a continuation of the discussion here:
>> http://issues.apache.org/bugzilla/show_bug.cgi?id=32806
>> 
>>      Ben, I understand the example you posted as comment #8 but I
>> feel this is best handled in release notes. You should dedicate a
>> section to "migration notes" and discuss this and many other concerns.
>> I'm sure case-sensitivity is only one of many potential concerns with
>> migrating or upgrading Tomcat. Aside from the example you gave (caused
>> by migration) are there any other security concerns?
>> 
>> Thank you,
>> Gili
>
>To be honest with you, I don't know.  I, personally, prefer case
>sensitive environments.  With the exception of IIS, I've never had to
>work with an app server that wasn't case-sensitive.  When I type 'a', I
>mean 'a', not ('a' or 'A').  For that reason, I've never researched the
>issue.
>
>Since the naming convention in Java depends on case-sensitivity, I
>suspect that the majority of Servlet/JSP developers feel the same way.
>
>Pursue it if you like but I suspect it will fall on deaf ears, both here
>and with the Spec group.  
>
>When in Rome..... ;)

        hehe. Agreed. I admit it is a subjective thing, and exactly for
that reason I think I should have the option/ability to make Tomcat
work the way I personally prefer. I will pursue the issue further with
the specification team :)

        Funny you should bring up Java being case-sensitive. My first
programming languages were BASIC and (Turbo) Pascal. While I disliked
the former, I liked the latter. I really like Java a lot, but I still
hold the view that case-sensitivity is a silly concept for
file-systems, programming languages, etc. I agree 100% with you that
when I say 'a' I mean 'a' and not 'A' and I don't want some nitwit
coding using 'a myClassA' when I declare 'class A'. Still, my view is
that this is a coding style sort of thing and just like the compiler
does not flag compiler errors for poor coding style, it should not flag
errors for people ignoring case sensitivity. I would further suggest
that case sensitivity issues are best handled by the IDE
(code-formatter, etc) and not in the compiler level. Just like
code-formatters fix "bad style" they should handle case sensitivity all
over the place to make sure people use the same casing everywhere. Bad
style is not a compiler error :)

Gili

Reply via email to