in reply to Re: Why isn't C<use strict> the default?
in thread Why isn't C<use strict> the default?

I guess I would 'fix' that problem by including an extra prompt that would be displayed when an AM or new member (say their first 10 posts), posts a SoPW that read:

Is your problem related to the (possibly sudden) appearance of errors like:

  • "Global symbol "$x" requires explicit package name at ..."?

    Are you using, or did you just install version 5.x.strict of Perl?

    Have you tried adding "no strict" to the top of your program?

    You must answer these questions before continuing.

    If you answer "Yes, Yes, No" to these 3 questions your question will not be submitted.

    If you answer otherwise, but it then transpires that you lied, your question will be summarially deleted and ignored.

    If adding "no strict" fixes your problem, but you would like to learn how to avoid using it, then Welcome to the Monastery.

    • Hmm. Probably need a lawyer (or just someone competent with English!) to get the wording just right. Or maybe that's just too selfish? :)

    Examine what is said, not who speaks.
    "Efficiency is intelligent laziness." -David Dunham
    "Think for yourself!" - Abigail
    "Memory, processor, disk in that order on the hardware side. Algorithm, algorithm, algorithm on the code side." - tachyon
    • Comment on Re^2: Why isn't C<use strict> the default?

    Replies are listed 'Best First'.
    Re^3: Why isn't C<use strict> the default?
    by Anonymous Monk on Oct 28, 2004 at 17:12 UTC
      What makes you think that someone who doesn't know what 'strict' does really wants to avoid using "no strict", if "no strict" solves his problem?

      All you do is cargo cult "no strict" into every bad program! Hurray, a great victory!

    		[reply]
        What makes you think...

        Cos some people are curious enough to wonder...

        All you do is cargo cult "no strict" into every bad program!

        And the difference between a 'bad program with "no strict" cargo culted in' and a 'bad program' is...?

        Hurray, a great victory!

        victory?

        Examine what is said, not who speaks.
        "Efficiency is intelligent laziness." -David Dunham
        "Think for yourself!" - Abigail
        "Memory, processor, disk in that order on the hardware side. Algorithm, algorithm, algorithm on the code side." - tachyon
    		[reply]
          Cos some people are curious enough to wonder...

          Curious people whould have read a book or the documentation before starting to program, and whould have known about strict already.

          And the difference between a 'bad program with "no strict" cargo culted in' and a 'bad program' is...?

          Nothing, so no reason to break existing programs by making strict the default.

    		[reply]

    In Section Meditations