What is in $b? Where is $CMB? Why do you expect the value stored in a hash to change once it's been set? Why are you not rolling the die each time the user inputs a request?
If the computer were a person, here is what that person is doing currently:
- Roll a die, and write down the result.
- Roll another, and write down the result.
- Roll again and write down the result.
- Read the first result and write it again into a little book of indexes and corresponding values.
- Read the second result and write it again into a little book of indexes and corresponding values.
- Read the third result and write it again into a little book of indexes and corresponding values.
- Repeatedly ask someone what they would like to know.
- Look in your little index book and find the answer that was written down for the question that was asked.
- Read back to the user the answer that you wrote in your little book.
- Wonder why the answer written in the little book hasn't been magically erased and re-written without your intervention.
In real life, as a person, you would roll the dice each time someone requests a roll. In your program, you roll just one time and store the result. I don't think that caching a die roll is the right approach.
-
Are you posting in the right place? Check out Where do I post X? to know for sure.
-
Posts may use any of the Perl Monks Approved HTML tags. Currently these include the following:
<code> <a> <b> <big>
<blockquote> <br /> <dd>
<dl> <dt> <em> <font>
<h1> <h2> <h3> <h4>
<h5> <h6> <hr /> <i>
<li> <nbsp> <ol> <p>
<small> <strike> <strong>
<sub> <sup> <table>
<td> <th> <tr> <tt>
<u> <ul>
-
Snippets of code should be wrapped in
<code> tags not
<pre> tags. In fact, <pre>
tags should generally be avoided. If they must
be used, extreme care should be
taken to ensure that their contents do not
have long lines (<70 chars), in order to prevent
horizontal scrolling (and possible janitor
intervention).
-
Want more info? How to link
or How to display code and escape characters
are good places to start.
|
