I don't want to require the installation of non-core modules. If there is not a better way to do this, my next version release will abandon all of those useful tests

You could pull this off with a little monkey patching and finagling but I think you're getting lost in the weeds again... Why on Earth would you avoid a module that has been in the perl core for almost eight years or make your test suite less complete for the arbitrary goal of supporting perl versions that are statistically irrelevant in 2023? Who are you targeting that stopped installing new versions of the interpreter 19 years and 11 months ago with v5.8.3? And if this person exists, why would they avoid updating perl itself-- ignoring two decades of improvements, security fixes, and features --only to install your brand new non-battle-hardened module tomorrow?

And if a module was non-core 8 years ago (or even today), so what? Your module is non-core. You put that code on CPAN because it serves a practical purpose and you want your work to be found, installed, used, and potentially improved upon by others; not avoided or ignored because it's not a core module. The CPAN itself wouldn't make much sense if we all avoided using each other's non-core modules. Besides, worrying that someone doesn't have a module "new" to the core or an entirely non-core module (or even a given version of a core or non-core module) pre-installed is a problem resolved long ago: properly define your prerequisites in metadata and, better yet, in a cpanfile.

Finally, the very first line of Test::More reads "STOP! If you're just getting started writing tests, have a look at Test2::Suite first." Emphasis is theirs. I'd take the advice because Test2 is where the effort is going today and in the future.

In reply to Re: How to create and install a module compatible with both UTF8 and Perl 5.8.3 without using non-core modules? by SankoR
in thread How to create and install a module compatible with both UTF8 and Perl 5.8.3 without using non-core modules? by Polyglot

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.