The following is a generalization, but hopefully it's clear enough.

I have a two packages, Foo::Bar and Foo::Batz. I have a sub called Plop which will create an object in one of these packages, based on it's argument in the statement. But the following code fails me, with a "Bad Name after Package::" error. 
use strict;
require 'foo_bar.pl';  #currently using require for these
require 'foo_batz.pl'; #intention is to fold them into the 
                       #script after development 
my @Stack = ();
my $type = "Bar" || "Batz";
do_phu($type);

sub do_phu {
    my $class = shift;
    my $temp_obj = Foo::$type->new();
    push( @Stack, $temp_obj ); # point of failure
}

[download]
The answer to this is probably right in front of my face, but I'm stuck. I know there must be an alternative that doesn't involve a lot of if-thens.

Thanks in advance for any help!

In reply to Scalar in Method Call by ichimunki

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.