I imagined the second solution:

my $obj = 'Parent'->new;
$obj->populate(@data);
for my $child_class (@possible_child_classes) {
    if (my $new = $child_class->new_from_parent($obj)) {
        $obj = $new;
        last
    }
}
# Don't forget to handle the case that $obj hasn't changed.
[download]

In fact, the only problem why this shouldn't go to the parent class is the array of possible child classes. So, get it from outside; the parent can insist on its children implementing a method:

sub new_from_parent { die "Should be overriden.\n" }

sub rebless {
    my $self = shift;
    my @possible_child_classes = @_;
    for my $child_class (@possible_child_classes) {
        # etc. using $self instead of $obj.
[download]

And the code becomes

my $obj = 'Parent'->new;
$obj->populate(@data);
$obj->rebless(@possible_child_classes);
[download]

---

---

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! —

• How do I compose an effective node title?
• How do I post a question effectively?
• Markup in the Monastery

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:
	&		&
	<		&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.