Update: Anonymous Monk answered in the meantime here, pointing back to his/her previous post. So Spiffy is involved ... it seems it doesn't play nice with perlapp ...

Spiffy is involved...whats the suggested method to remove the use of Spiffy from the module?

I very much doubt that you'll be able to remove Spiffy from the module. Spiffy tends to become very closely entwined with the code that uses it.

I suggest that you report the problem to the author. Hopefully he'll then pass it on to the author of Spiffy.

--
<http://dave.org.uk>

"The first rule of Perl club is you do not talk about Perl club."
-- Chip Salzenberg

There seems to be some scoping confusion going on here. Please post a short (<30 lines) program that demonstrates this problem.

I appreciate any insight you may have. This is related to an earlier post regarding my sub error. Here is a simple script that re-creates the error using PerlApp:

use strict;
use warnings;

use WWW::Myspace;
use Contextual::Return::Failure;

my ($account, $password) = retrieve_acct_info();

my $myspace = WWW::Myspace->new($account,$password);

sub retrieve_acct_info {

    my $account = 'email';
    my $password = 'password';

    return ($account, $password);
}
[download]

The error is:

"my" variable $self masks earlier declaration in same scope at test.pl
+ line 11, <DATA> line 21937.
[download]