Chuck,

1. You're more than welcome (x8)! :o)
2. Btrott has a VERY good point! If you're dealing with a big hash you could get slugish in NO time.

But then again, (I shall say this perl style)
if (you're running a big hash) {
  it's probably because you're pulling 
  something off from a text file;
    if (that's true) {
      then your text file shouldn't be 
      too big anyway;
    } else {
      its going to get slugish from the 
      filesystem access in the first place!;
    }
} else {
  you should be considering a comercial
  database product, under which you wouldn't
  need to do case detection on your hash;
}

[download]

Was that reasonably readable? In any case, I'm glad I could be of assistance!

Cheers again!

In reply to Ooops! But not... by BBQ
in thread Case insensitivity in a hash... Futile effort? by ChuckularOne

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.