Re^3: You cannot pass args when calling inner() in Moose?

Why would it matter if there is not necessarily an inner class? Assuming the i attribute does not clobber any existing attribute, then this becomes a no-op.

And according to Moose::Manual::BestPractices, you should Always_call_inner_in_the_most_specific_subclass

Comment on Re^3: You cannot pass args when calling inner() in Moose? Download Code

Replies are listed 'Best First'.
Re^4: You cannot pass args when calling inner() in Moose? by metaperl (Curate) on Jul 21, 2011 at 19:03 UTC
For the time-being, I have if-then'ed a solution: `sub updateprogress { my ($self) = @_; return unless $self->progressbar; my $frac = frac($self->recordi, $self->recordcount); $self->progressbar->set_fraction($frac->num); }` [download] and then the data processing loop blindly calls this graphic method: `sub manager { my ($Operation) = @_; my @row = $Operation->getnew; my ( @warnings, @fatals ); $Operation->recordi(0); for my $row (@row) { $Operation->recordi( $Operation->recordi + 1 ); $Operation->data($row); $Operation->process; $Operation->updateprogress; } ( \@warnings, @fatals ); }` [download] The mantra of every experienced web application developer is the same: thou shalt separate business logic from display. Ironically, almost all template engines allow violation of this separation principle, which is the very impetus for HTML template engine development. -- Terence Parr, "Enforcing Strict Model View Separation in Template Engines"	[reply] [d/l] [select]

Replies are listed 'Best First'.

Re^4: You cannot pass args when calling inner() in Moose?
by metaperl (Curate) on Jul 21, 2011 at 19:03 UTC

sub updateprogress {
    my ($self) = @_;
    return unless $self->progressbar;

    my $frac = frac($self->recordi, $self->recordcount);
    $self->progressbar->set_fraction($frac->num);
}
[download]

sub manager {
    my ($Operation) = @_;

    my @row = $Operation->getnew;

    my ( @warnings, @fatals );
    $Operation->recordi(0);
    for my $row (@row) {
        $Operation->recordi( $Operation->recordi + 1 );

        $Operation->data($row);
        $Operation->process;

    $Operation->updateprogress;
    }
    ( \@warnings, @fatals );
}
[download]

The mantra of every experienced web application developer is the same: thou shalt separate business logic from display. Ironically, almost all template engines allow violation of this separation principle, which is the very impetus for HTML template engine development.

-- Terence Parr, "Enforcing Strict Model View Separation in Template Engines"

[reply]
[d/l]
[select]