Go with lc.

If this hash only holds filehandles and the rest of the user info is stored elsewhere then just store lowercased nicks and look up lowercased nicks, like Juerd++ suggested.

If you really have reason not to do that, then you should use an array (or a pair of arrays) since that's more efficient to step through than a hash. However, remember that avoiding the expensive stepping through arrays to find a single value is what hashes were made for. Anyway, if you stick with that approach, do my $nick = lc shift; first so you don't need to repeatedly lowercase the nick within the loop, then use return $nick_check if $nick eq lc $nick_check; rather than a regex.

Makeshifts last the longest.

In reply to Re: Problem With Perl IRC Server by Aristotle
in thread Problem With Perl IRC Server by Veachian64

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.