in reply to Re: Use strict warnings and diagnostics or die
in thread Use strict warnings and diagnostics or die

Although the general convention is to use lower_case type varnames in Perl the case sensitivity of varnames can leadToProblems if you are using camel hump notation and have a case inseneitive Windows type background.

Bugs related to poorly scoped common varnames like $i, $j, $count, $timeout or often $_ can be also very difficult to isolate in my experience unless you are fortunate with the bug report.




  • Comment on Re: Re: Use strict warnings and diagnostics or die

Replies are listed 'Best First'.
Re: Use strict warnings and diagnostics or die
by jonadab (Parson) on Feb 04, 2003 at 03:49 UTC

    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.