file a bug report with author

I considered that and checked the CPAN Testers Matrix but don't see any failures for L! I figured maybe L was doing something unintentional by loading non-methods that a perlbug allowed to happen all this time? L docs are sparse. Why else would Perl remove a way to do it? Since L is maintained it doesn't seem to be considered a bug.

Anyway I just saw davido's reply too and must say L is black magic to me. I don't even know what it's doing, nor if this is a bug in L, let alone how to fix it or anything. I just love L and want to keep up with new Perl versions and hope someone will post a patch so my local L will autoload non-methods again, without any warnings! 🙏 Thanx 😇

In reply to Re^2: Perl 28 broke L: How to fix? by Anonymous Monk
in thread Perl 28 broke L: How to fix? by Anonymous Monk

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.