Beefy Boxes and Bandwidth Generously Provided by pair Networks
Pathologically Eclectic Rubbish Lister

Comment on

( #3333=superdoc: print w/replies, xml ) Need Help??
You're free to use another implementation if you don't want to use perl's

I wasn't trying to imply that I have a better recommendation - I don't.
Personally, I will just use lc(), as it is quite adequate for the situations in which I use it.
However, just as there are situations in which lc() does not do the right thing, there are also portability issues with fc() - and I think it would have been better if you had mentioned those portability issues when you said that "fc should be used for case-insensitive comparisons, not lc".

I suspect that *you* are so well aware of that portability issue, that it didn't even occur to you to mention it.
But dumb pricks like me are not so quick on the uptake, especially when the crucial information is held back until the very end of the documentation (not your fault).

This is one of the interesting aspects of the way that Larry Wall has "stitched up" perl5.
In a normal situation, if there were a number of features that we wished to add to perl, the porters would just release a new version of perl named "perl-6.0.0" - a version of perl that provided those new features whilst promising no compatibility (yet providing extensive compatibility) with perl-5.x.x.
But Larry has successfully (and with deliberate intention) ensured that can't happen.
Therefore, in accordance with the backward-compatibility of perl-5.x.x, the only way that new features can be added is via 'use feature'.
I expect that, by about perl-5.36.0, the recommendation will no longer be that you start your perl script with:
use strict; use warnings;
Rather, it will be that you begin your scripts with:
use strict; use warnings; use feature ':5.26.0';
And, with 5.46.0, you begin your scripts with:
use strict; use warnings; use feature ':5.36.0';
... or something along those lines.

The disappointing thing about that is that there's a large number of monks here (1nickt ++ is a notable exception) who think that's completely acceptable.


In reply to Re^5: Can we make hash key check in 'if' condition case insensitive? by syphilis
in thread [SOLVED: Can we make hash key check in 'if' condition case insensitive? by Perl300

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, 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, 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.
  • Log In?

    What's my password?
    Create A New User
    and all is quiet...

    How do I use this? | Other CB clients
    Other Users?
    Others cooling their heels in the Monastery: (5)
    As of 2018-03-24 16:53 GMT
    Find Nodes?
      Voting Booth?
      When I think of a mole I think of:

      Results (299 votes). Check out past polls.