use Perl

• Re; Moose (Score:1)

  by Stevan (6065)

  Well, Moose is not really doing anything very nasty here, the class loading code is quite sane (we "borrowed" it from Class::Inspector). But we are looping through @_ using $_ when we load those classes, so that is where the issue comes from.

  I have adjusted all code that comes in contact with the class loader so that none of it uses $_ anymore. This should eliminate the issue you are seeing with the Exporter::NoWork and modules like it. This will be available in the next release of Class::MOP/Moose.

  -
  • Re:Re; Moose (Score:2)

    by Ovid (2709) on 2008.02.26 11:21 (#61341) Homepage Journal

    I don't think it's terribly nasty, but the implicit aliasing can cause strange behavior if other modules don't play well with that. Imagine this:

    foreach (@_) {
        some_other_function($_);
        # do something with $_
    }

    If some_other_function did something silly like s/(.*)/scalar reverse $1/e, then the above code would break. Guarding against side-effects is a good thing. Of course, since @_ contains aliases, I suppose that the way to be truly paranoid would be:

    foreach my $var (@_ = @_) {
        some_other_function(my $temp = $var);
        # do something with $var
    }

    After a while, too much paranoia on my part would get ridiculous, but I'm now understanding better why Larry Wall rejected my proposal to add an 'is rw' shortcut for sub/method signatures in Perl 6 (right now you have to declare this for every argument and that gets tedious, but it's the right thing to do).

    Reply to This

    Parent