I'm calling:
my $rand_bloom = new Bloom::Faster({m => 1048576, k => 4});
It's pretty normal, I think, and I don't think it would be possible to get
to line 73 unless m and k were defined. It must be complaining about n and
e.
Excerpt from Faster.pm:
67 if (! (ref $data)) {
68 $struct{vector} = bdeserialize($data);
69 } else {
70 if (defined($data->{e}) && defined($data->{n})) {
71 $struct{vector} = binit_sugg($data->{n},$data->{e});
72 } *elsif (defined($data->{m}) && defined($data->{k})) {*
73 $struct{vector} =
binit($data->{m},$data->{k},$data->{n},$data->{e});
74 } else {
75 $! = "invalid arguments to Bloom::Faster";
76 return undef;
77 }
On Sun, May 9, 2010 at 2:37 PM, Peter Alvaro via RT <
bug-Bloom-Faster@rt.cpan.org> wrote:
Show quoted text> <URL:
https://rt.cpan.org/Ticket/Display.html?id=57323 >
>
> On Sun May 09 14:28:07 2010, demoss.matt@gmail.com wrote:
> > Use of uninitialized value in subroutine entry at
> > /usr/lib/perl5/site_perl/5.10/i686-cygwin/Bloom/Faster.pm line 73.
> >
> > I get this when I call new with m and k.
>
> Are you certain m and k are initialized? This is the first mention of this
> issue and the current
> Bloom::Faster release has been in production for some time.
>
> Please send along the enclosing code to the call to 'new'. I do not have a
> windows/cygwin
> environment to test in, unfortunately, so hopefully it's not something
> specific to that
> environment.
>
RT for rt.cpan.org