I don't see a compelling argument either way.
Assuming the situation I posit holds, the reader or user will, of necessity, have consulted the documentation for the modules that would, of course, speak to matters relevant to "what can I do with this thingy". It pretty much follows from the posited situation that the possible values of ref($obj) are closely related in some useful manner, so as to permit generalization. Heck, they may all have an identical set of methods, differing only in how those methods do stuff.
If I am in a situation where I need "another ref($obj)", I, in my laziness, don't want to be forced to say ref($obj) just for the sake of truth and beauty. I do not see that having "new" take the ref() if necessary as being, per se, a Bad Thing.
Perhaps we will have to agree to disagree.
yours,
Michael
In reply to Re: (Re:) $class = ref $class || $class
by herveus
in thread Constructor/Factory Orthodoxy
by mojotoad
| For: | Use: | ||
| & | & | ||
| < | < | ||
| > | > | ||
| [ | [ | ||
| ] | ] |