Using package constant to define your named constants, is somewhat more efficient that using a hash to perform the mapping:

#! perl -slw use strict; use Benchmark qw[ cmpthese ]; package C; use constant { RED => 0xFF0000, BLUE => 0x00FF00, GREEN => 0x0000FF, }; package main; use constant { RED => 0xFF0000, BLUE => 0x00FF00, GREEN => 0x0000FF, }; my %colors = ( RED => 0xFF0000, BLUE => 0x00FF00, GREEN => 0x0000FF, ); open STDERR, ">nul"; cmpthese -1, { hash => sub{ warn $colors{ RED }, $colors{ BLUE }. $colors{ GRE +EN }; }, m_const => sub{ warn RED, BLUE. GREEN; }, p_const => sub{ warn C::RED, C::BLUE. C::GREEN; }, }; __END__ P:\test>junk Rate hash m_const p_const hash 116531/s -- -11% -12% m_const 130636/s 12% -- -1% p_const 132428/s 14% 1% -- P:\test>junk Rate hash p_const m_const hash 116531/s -- -9% -10% p_const 128577/s 10% -- -1% m_const 129366/s 11% 1% -- P:\test>junk Rate hash m_const p_const hash 116642/s -- -10% -10% m_const 129468/s 11% -- -0% p_const 129590/s 11% 0% --

If you're concerned with the namespace pollution of having 7000 constants in your main package (though if you make them all uppercase it precludes most possibilities of collisions), then you could place them into separate (short-named) package and invoke them via their full names as in m_const above.


Examine what is said, not who speaks -- Silence betokens consent -- Love the truth but pardon error.
Lingua non convalesco, consenesco et abolesco. -- Rule 1 has a caveat! -- Who broke the cabal?
"Science is about questioning the status quo. Questioning authority".
The "good enough" maybe good enough for the now, and perfection maybe unobtainable, but that should not preclude us from striving for perfection, when time, circumstance or desire allow.

In reply to Re: Getting numeric value of a alphabetic string by BrowserUk
in thread Getting numeric value of an alphabetic string by chakkaln

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.