I do have a case-insensitive background (cut my teeth
on PC-DOS 3.3), but while the case sensitivity in my
ext3 filesystem occasionally bugs me, I have never had
any trouble with case-sensitive variable names. Most
of the computer languages I have used (with the notable
exception of BASIC, which admittedly I did use quite a
bit) are case-sensitive, so I naturally think of
variables as case-sensitive.
But your example is good nonetheless. I said that
the scenerio seems unlikely to me, but unlikely is not
the same as silly (which is what I formerly thought
of the idea, having seen numerous flawed examples and
no good ones).
Other things (such as Taint mode) are higher on my
list, but I now intend at some point to teach myself
to use strict.
It's odd, I came into this thread expecting not
to have my mind changed, and it (at least partly) was.
I went into the discussion about exception-handling
expecting to have someone show me what I was missing,
and having read the best explanations offered I'm now
more sure than ever that I was right about that one.
Are you posting in the right place? Check out Where do I post X? to know for sure.
Posts may use any of the Perl Monks Approved HTML tags. Currently these include the following:
<code> <a> <b> <big>
<blockquote> <br /> <dd>
<dl> <dt> <em> <font>
<h1> <h2> <h3> <h4>
<h5> <h6> <hr /> <i>
<li> <nbsp> <ol> <p>
<small> <strike> <strong>
<sub> <sup> <table>
<td> <th> <tr> <tt>
Snippets of code should be wrapped in
<code> tags not
<pre> tags. In fact, <pre>
tags should generally be avoided. If they must
be used, extreme care should be
taken to ensure that their contents do not
have long lines (<70 chars), in order to prevent
horizontal scrolling (and possible janitor
Want more info? How to link
or How to display code and escape characters
are good places to start.