There's only sence to your class bless for other classes (when you get $class as an object), if this other class can inherit over your class. So, if you get an object blessed into the main package, like your example, your package shouldn't create a object for it.

I think that to keep OO ok you should declare new() as:

sub new { my $class = ( @_ ? ( ref($_[0]) ? ( UNIVERSAL::isa($_[0] , __PACKAGE__ +) ? ref(shift(@_)) : __PACKAGE__ ) : ( $_[0] =~ /^\w+(?:::\w+)*$/ ? shift +(@_) : __PACKAGE__ ) ) : __PACKAGE__ ) ; my $this = bless {}, $class ; ## initialyze code... return $this ; }

I know that is not a beautiful code, but to do what you want is that.

Graciliano M. P.
"Creativity is the expression of the liberty".


In reply to Re: Is "ref($class) || $class" a bad thing? by gmpassos
in thread Is "ref($class) || $class" a bad thing? by stvn

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.