On Jan 28, 2008 11:56 PM, Michael G Schwern <[EMAIL PROTECTED]> wrote:
> To resolve this, I propose we change the procedure from calling
> $self->depends_on(@dependents) to $self->depends_for($current_action).  For
> example...
>
>         sub ACTION_test {
>                 my $self = shift;
>
>                 $self->depends_for('test');

I like it.  I'd change the name to invoke_dependencies() or something
though, to make it clear that we're not declaring, we're invoking (the
current code does both).

But, the problem is that sometimes you need to invoke different
dependencies at different times.  The 'testcover' action does this, it
calls 'code' early and 'test' late.  I don't know if it really needs
to (since 'test' depends on 'code') but since it uses action at a
distance, it's possible.  'ppmdist' also calls two dependencies
separated by some code.

Maybe we could add the new stuff you're proposing, and allow the old
usage too when necessary.

 -Ken

Reply via email to