Because a common idiom used to "solve" the "class or object method?" question, can lead to odd behavior when a constructor is called as a function and not a method.

I disagree:

#!/usr/bin/perl -w use strict; use Test::More tests => 2; package Foo; sub new { my $class = shift; bless {}, $class; } sub test { 1; } package Bar; sub new { my $class = shift; $class = ref( $class ) || $class; bless {}, $class; } sub test { 1; } package main; sub test { 0; } my $foo = Foo::new(); ok( $foo->test() ); my $bar = Bar::new(); ok( $bar->test() );

That's the same behavior regardless of the "class or object?" check. This leads me to conclude that that check has no bearing on the behavior. What leads you to believe otherwise?


In reply to Re^7: Is "ref($class) || $class" a bad thing? by chromatic
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.