[Disclaimer:
I am not a user of SDL and I do not have it installed.
The following is untested guesswork (actually, perl -c says "syntax OK", but untested beyond that).]
After looking at your posted code, I had a similar thought to what ++bliako wrote.
I can see that you've copied the code from
"[PDF] SDL::Manual":
a visual inspection shows no problems there.
Try replacing this entire call:
$app->add_event_handler(sub {
...
});
with
{
my %paddle_move;
my $key_joiner;
BEGIN {
$key_joiner = '~';
%paddle_move = (
SDL_KEYDOWN . $key_joiner . SDLK_UP, -2,
SDL_KEYDOWN . $key_joiner . SDLK_DOWN, 2,
SDL_KEYUP . $key_joiner . SDLK_UP, 0,
SDL_KEYUP . $key_joiner . SDLK_DOWN, 0,
);
}
$app->add_event_handler(sub {
my $event = shift;
my $paddle_key = $event->type . $key_joiner . $event->key_sym;
if (exists $paddle_move{$paddle_key}) {
$player1->{v_y} = $paddle_move{$paddle_key};
}
});
}
That will set up all of the possible values for $player1->{v_y} once, at compile time.
Assigning those values now only requires a single if condition,
instead of the multiple if and elsif conditions you currently have.
-
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.