Interesting code you have there - i can't tell if it's a hack on the decorator pattern or maybe even the state pattern. At any rate, i think i see what the goal is:

You instantiate the First class and test to see if it does the job, if it doesn't, revert to the Second class. This is cool, but it's a maintenance nightmare should you decide to add a Third, or a Fourth, ... all the way to the Nth possible class.

I rewrote your code and added some tests - here is the solution domain: 

0-5: fail
6-9: second handles
10-: first handles

[download]
And the code: 
use strict;
use Data::Dumper;

package First;

sub new { 
   my $class = shift;
   my $self  = {
      foo => 'bar'
   };
   return bless $self, $class;
}

sub test {
   my $self = shift;
   my $arg  = shift || 10;
   return ($arg > 9) ? "okay" : bless $self, 'Second';
}

package Second;

sub new { 
   my $class = shift;
   my $self  = {
      foo => 'qux'
   };
   return bless $self, $class;
}

sub test {
   my $self = shift;
   my $arg  = shift || 4;
   return ($arg > 5) ? "okay" : undef;
}

package main;

my $arg = shift || 10;
my $t   = First->new();

if (ref $t->test($arg)) {
   warn "first failed, trying second...";
   die "second failed" unless $t->test($arg);
}

print (ref $t, " passed\n");

print Dumper $t;

[download]
Try it out. Notice the very last expression which outputs the Dump of the object - notice how even though it might belong to package First or Second - $self is the same. That may or may not be a problem for you, because the technique to change $t from First to Second only changes it's package, not it's attributes.

In conclusion, the only two problems i see are

  1. extensibility - need to generalize First, Second, Third, etc.
  2. not inheriting attributes from oringal class - but this might your 'feature' ...
Three cheers for flexiblity!

jeffa 

L-LL-L--L-LL-L--L-LL-L--
-R--R-RR-R--R-RR-R--R-RR
F--F--F--F--F--F--F--F--
(the triplet paradiddle)

In reply to (jeffa) Re: Replacing namespaces by jeffa
in thread Replacing namespaces by smferris

Title:
Use:  <p> text here (a paragraph) </p>
and:  <code> code here </code>
to format your post, it's "PerlMonks-approved HTML":


  • Posts are HTML formatted. Put <p> </p> tags around your paragraphs. Put <code> </code> tags around your code and data!
  • Titles consisting of a single word are discouraged, and in most cases are disallowed outright.
  • Read Where should I post X? if you're not absolutely sure you're posting in the right place.
  • Please read these before you post! —
  • Posts may use any of the Perl Monks Approved HTML tags:
    a, abbr, b, big, blockquote, br, caption, center, col, colgroup, dd, del, details, div, dl, dt, em, font, h1, h2, h3, h4, h5, h6, hr, i, ins, li, ol, p, pre, readmore, small, span, spoiler, strike, strong, sub, summary, sup, table, tbody, td, tfoot, th, thead, tr, tt, u, ul, wbr
  • You may need to use entities for some characters, as follows. (Exception: Within code tags, you can put the characters literally.)
            For:     Use:
    & &amp;
    < &lt;
    > &gt;
    [ &#91;
    ] &#93;
  • Link using PerlMonks shortcuts! What shortcuts can I use for linking?
  • See Writeup Formatting Tips and other pages linked from there for more info.