Re^2: no binary decoder!

Replies are listed 'Best First'.
Re^3: no binary decoder! by tachyon (Chancellor) on Oct 27, 2004 at 01:50 UTC
It means that you need to debug it, bacause it works for me. As noted the only logical explanation would seem to be stomping on that global hash. It is a very easy path trace that sould be trivial to debug. It won't debug itself. I suggest that there is a problem with the MailScanner application that is using MIME::Tools as both Perl and this Package are pretty damn stable. As suggested put in some debugging code and see what the problem is. `At the top of the module put: my $DEBUG = 1; $DEBUG && require Data::Dumper; # them place statements like these $DEBUG && warn Data::Dumper::Dumper(\%hash); $DEBUG && warn "Sub foo() got @_\n";` [download] Once you have found and fixed the problem set $DEBUG = 0; and that code will become inactive. cheers tachyon	[reply] [d/l]

Replies are listed 'Best First'.

Re^3: no binary decoder!
by tachyon (Chancellor) on Oct 27, 2004 at 01:50 UTC

It means that you need to debug it, bacause it works for me. As noted the only logical explanation would seem to be stomping on that global hash. It is a very easy path trace that sould be trivial to debug. It won't debug itself. I suggest that there is a problem with the MailScanner application that is using MIME::Tools as both Perl and this Package are pretty damn stable. As suggested put in some debugging code and see what the problem is.

At the top of the module put:

my $DEBUG = 1;
$DEBUG && require Data::Dumper;

# them place statements like these

$DEBUG && warn Data::Dumper::Dumper(\%hash);
$DEBUG && warn "Sub foo() got @_\n";
[download]

Once you have found and fixed the problem set $DEBUG = 0; and that code will become inactive.

cheers

tachyon

[reply]
[d/l]