comment on

While I am waiting for a review of my proposed patch, I'd like to hear the thoughts of my fellow monks if this is a desirable option to have.

Try these bookmarks I had for some stackoverflow question

Is it documented and tested? If documented or tested, its fine, otherwise, its a mistake :)

Is "ref($class) || $class" a bad thing?

Re^15: $class = ref $class || $class (not me) , Constructor/Factory Orthodoxy
Why ref($proto) should be avoided
ref($proto) - just say no!
Re^3: OOP first-timer shouldn't use ref $proto || $proto :)
Is "ref($class) || $class" a bad thing?
$class = ref $class || $class
(Re:)+ $class = ref $class || $class

Along with the bookmarks was my note I found "clever"

i believe the official recommendation is, if you're not using Moose/Mo/Badger...otheroopyhelpers... do whatever you want, you're doing it wrong anyway, its your time to waste

In reply to Re: $class = ref($class) if ref($class) Redux by Anonymous Monk
in thread $class = ref($class) if ref($class) Redux by boftx

Are you posting in the right place? Check out Where do I post X? to know for sure.
Posts may use any of the Perl Monks Approved HTML tags. Currently these include the following:
<code> <a> <b> <big> <blockquote> <br /> <dd> <dl> <dt> <em> <font> <h1> <h2> <h3> <h4> <h5> <h6> <hr /> <i> <li> <nbsp> <ol> <p> <small> <strike> <strong> <sub> <sup> <table> <td> <th> <tr> <tt> <u> <ul>
Snippets of code should be wrapped in <code> tags not <pre> tags. In fact, <pre> tags should generally be avoided. If they must be used, extreme care should be taken to ensure that their contents do not have long lines (<70 chars), in order to prevent horizontal scrolling (and possible janitor intervention).
Want more info? How to link or How to display code and escape characters are good places to start.


laziness, impatience, and hubris
	PerlMonks