in reply to iis ftp redirection

quick and dirty, didn't use strict

Do you have any reason not to use strict or warnings? This script is large enough that I would be unwilling to maintain or enhance it without use strict in place.

Have you wasted any time debugging typos that strict would have found? This nearly always justifies starting off with strict - it certainly does for me.

--

Oh Lord, won’t you burn me a Knoppix CD ?
My friends all rate Windows, I must disagree.
Your powers of persuasion will set them all free,
So oh Lord, won’t you burn me a Knoppix CD ?
(Missquoting Janis Joplin)

Replies are listed 'Best First'.
Re^2: iis ftp redirection
by 3dbc (Monk) on Mar 23, 2006 at 04:25 UTC
    I don't use strict because perl doesn't and didn’t require me to.

    I can appreciate strict when considering maintenance within the perl community and that ideal is probably what makes perl such a great portable language with so many useful modules. But since I haven’t written any modules yet and am evolving my understanding of the perl global community this is just one small contribution for all it has done for me.

    I like perl compared to VBS because it doesn't have as many strict rules although VBS is powerful in its own right on windows systems. Perl is different especially when compared to Microsoft based languages WSH, ASP, .NET etc. and I like to be creative. Perl's flexible but yet a defined set of rules, without much restriction, is what attracts me to a programming language... somewhat similarly that is why I like PL/SQL over T-SQL. Microsoft languages have many more standard formalities, declarations... Perhaps my implementation is obscure and somewhat obfuscated according to strict implementations but it does what it says it does and it can be used on IIS 4, 5, 5.1 and 6 to disable anonymous access via IIS FTP.

    Is creative, useful, unconventional, functionality obscure and obfuscated and therefore frowned upon?
      Is creative, useful, unconventional, functionality obscure and obfuscated and therefore frowned upon?

      No, not using strict is just undisciplined. I feel pretty safe in saying that most good, creative, unconventional code is written by people who use strict strictly.

      When I was a VB programmer, it was easy to divide a line between "stuff that was crap" and "stuff that we don't know about yet but might be crap or might be great stuff" by whether it used Option Declare. So I just utterly disbelieve you. Go write great stuff. I love great stuff. But use strict and disable it only for those small parts where you know it's the best thing to do at that moment.

      ⠤⠤ ⠙⠊⠕⠞⠁⠇⠑⠧⠊

        "it was easy to divide a line between "stuff that was crap" and "stuff that we don't know about yet but might be crap or might be great stuff" by whether it used Option Declare."

        "Implicit variable declaration can make writing scripts faster and easier; at the same time, however, it can lead to subtle errors that are difficult to diagnose and fix." Does this definition contradict your statement? (Surprising since it is on M$ TechNet).