Since you don't use called_as_method things like OOorNO
and myargs have so many caveats on their usage as to make
them useless in the general case.
Did you read/run the code snippets in the EXAMPLES section of the POD? Did you read the BUGS section of the POD docs for Devel::Caller? 
As I said before I think mixing OO and functional/procedural
styles in this way is almost always a bad idea. I cannot
think of single instance in many years of coding where
something like this would be an appropriate solution.
In theory, it's not such a mix as it might seem. I submit that, as polymorphism is one of the core principles of OO, this kind of inheritable (there's another one); shareable; importable/exportable; polymorphic interface is more extensible and useful than you claim; and more focused too. 
Why the bizzare, and undocumented, coercion of undef
keys/values in coerce_array (which is badly named since it
takes a list of values, and returns a hashref)? undef and
the empty string are different values and should be treated
as such
The origin of this method's name has to do with what it does. One of the errors this helps avoid is also mentioned in the docs - "can't coerce array into hash at..." Be it as it may, I thought the name fitting when I wrote it that way.

You have a good point about the undef-empty string observation. That should certainly be addressed in the code. 
Something like is_called_as_method would be a better name for the OOorNO subroutine.
I don't know why I didn't see this, but as this was one of my primary questions (naming), I'm really grateful for your idea. 
You're subroutines fail in many cases. Consider:
   Foo::foo( Foo => 12 );
   Foo->foo( Foo => 12 );
Did you test this? It doesn't fail in my tests or examples (which show in fact this very thing.) 
--
Tommy Butler, a.k.a. TOMMY

In reply to Re: Re^3: Seeking Wisdom: proposed fix for a broken CPAN module by Tommy
in thread Seeking Wisdom: proposed fix for a broken CPAN module by Tommy

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.