Re^4: adding to hash/writing to file errors

Replies are listed 'Best First'.
Re^5: adding to hash/writing to file errors by toolic (Bishop) on May 05, 2008 at 17:08 UTC
One of the quickest ways to debug Perl code is to start placing `print` statements near where you are having trouble. For looking at the contents of array and hash variables, `use Data::Dumper;`. For example, to inspect values passed into a sub: `print Dumper(\@_);` [download] Taking another pass through your code, I see a couple of unusual things: `my %logins = shift;` [download] Inside a sub, shift will remove a single element from the `@_` array, not an entire hash as you may expect. See for yourself with: `print Dumper(\%logins);` [download] You may want to consider passing hashes by reference (see perlreftut). Another oddity is: `if ( $pass <=> $logins{$username} ) {` [download] What are you trying to accomplish there? Another recommendation is to take advantage of your modular approach by testing your individual subs.	[reply] [d/l] [select]

Replies are listed 'Best First'.

Re^5: adding to hash/writing to file errors
by toolic (Bishop) on May 05, 2008 at 17:08 UTC

print

For looking at the contents of array and hash variables, use Data::Dumper;. For example, to inspect values passed into a sub:

print Dumper(\@_);
[download]

Taking another pass through your code, I see a couple of unusual things:

    my %logins = shift;
[download]

Inside a sub, shift will remove a single element from the @_ array, not an entire hash as you may expect. See for yourself with:

print Dumper(\%logins);
[download]

You may want to consider passing hashes by reference (see perlreftut).

Another oddity is:

    if ( $pass <=> $logins{$username} ) {
[download]

What are you trying to accomplish there?

Another recommendation is to take advantage of your modular approach by testing your individual subs.