in reply to Re^8: Using a sting with a variable name
in thread Using a sting with a variable name

From a Perl (language!) point of view, there's no difference between a package variable that hasn't been used, and a package variable which is undefined. The following, after all, is a valid Perl program; it compiles and runs: 
   print $foo;

[download]
it may warn, but it's valid.

It only matters in the implementation, and in the few edge cases where you can poke into the underlaying implementation.

Replies are listed 'Best First'.
Re^10: Using a sting with a variable name
by ikegami (Patriarch) on May 11, 2009 at 18:32 UTC
    So why bother using use strict; if it doesn't matter whether a variable exists or not. That perl doesn't care says nothing about whether the programmer cares or not.

    Note I never said that the OP cares. I even said he might not ("I don't know if that's ok or not."). I'm just outlining the possibilities the OP might be interested in.

[reply]
[d/l]
[select]
      Considering this entire exercise is only going to work with package variables, and we have to disable strict 'refs' for it to work in the first place, I don't really get your remark about use strict;.

      Package variables are Perl4 left overs. The era predating strict. And lexicals. When Perl variables were much more like AWK or Shell.

      And do get your capitalization right when it matters. perl cares, because perl is the implementation. But in the language, Perl, you can use any package variable you want, at any time*, without making any declaration you intent to use the variable.

      *You may, however, be forced to use the fully qualified name.

[reply]
[d/l]
[select]

        I don't really get your remark about use strict;.

        use strict 'vars'; let's the programmer know that a variable they used doesn't exist. The programmer uses the pragma because they wish to know that (i.e. they care to know that).

        Therefore, it's a counterexample to your claims that existence doesn't matter except "in the few edge cases where you can poke into the underlaying implementation" is false.

        And do get your capitalization right when it matters.

        I did. perl "compiles and runs: print $foo;", not "Perl (language!)".

[reply]
[d/l]
[select]

In Section Seekers of Perl Wisdom