use Perl

• Precedence? (Score:2)

  by Dom2 (2981)

  Just looking at it, I'd guess that it's a precedence issue and you need some parens thrown in. This is what I get from B::Deparse.

    % perl -MO=Deparse -MReadonly -e 'Readonly my $CurrentUser = $ENV{SUDO_USER} || getpwuid $>'
    Type of arg 1 to Readonly::Readonly must be one of [$@%] (not scalar assignment) at -e line 1, at EOF
    -e had compilation errors.
    use Readonly;
    &Readonly(my $CurrentUser = $ENV{'SUDO_USER'} || getpwuid $>);

  So, not what I expected, but still an
  • Re: (Score:2)

    by Ovid (2709)

    It's a context error. Consider the first line:

    my $CurrentUser = $ENV{SUDO_USER} || getpwuid $>;

    That must be scalar context (in fact, the || forces the left side to be in scalar context). However, consider the new version:

    Readonly my $CURRENT_USER => $ENV{SUDO_USER} || getpwuid $>;

    We have a list, not an assignment, so we have list context. getpwuid $> in list context generates more than one value and Readonly recognizes that we're trying to use a scalar, so it dies. The fix is to fo
    • Re: (Score:1)

      by jjore (6662)

      I'm not so sure "lists in scalar context" is what you mean. The comma operator in scalar context does that and qw(...) looks like a funny kind of list that might use the comma operator.
• Nasty (Score:1)

  by Aristotle (5147)

  This is probably one of those times to say “Perl 6 will fix that.”

  (Besides providing for such as “is ro.”)