The author of ReadonlyX explains at length that he "improved" the API to be a "drop in replacement"

(--> https://metacpan.org/pod/ReadonlyX#ReadonlyX-vs.-Readonly)

And this aliasing of namespaces happens in his module

BEGIN { *ReadonlyX:: = *Readonly:: } package # hide from PAUSE Readonly; # I wish...

that's unfortunate to word it mildly.

Especially since the author explicitly admits incompatibilities. (quote: "break 16 years of code out there in Darkpan.")

When another module loads the original Readonly, different implementations and prototypes will collide.

This "collides" with my understanding of a "drop-in-replacement".

If you want to use ReadonlyX, force it to use it's own namespace.

If there is no option for that, file a feature request.°

Regarding the strong wording of the PC-Policy - which I also dislike for its style- I doubt it originates in PBP.

And it seems to me this module is also far newer (2016) than Damian's book (2005), so please stop referencing it as justification.

Cheers Rolf
(addicted to the 𐍀𐌴𐍂𐌻 Programming Language :)
Wikisyntax for the Monastery

°) I could also come up with a wrapper module which is fixing that by unaliasing the namespaces, but let's wait what the author says.


In reply to Re^3: Readonly vs ReadonlyX (bad style) by LanX
in thread Readonly vs ReadonlyX by rlauer

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.