It's Version 1.26
Here's the entire output. I don't think the line numbers are that helpful though, I'm pretty sure the problem is to do with socket(...) not actually opening/creating the socket, but as it doesn't seem to return any error codes and I'm not sure what it is doing under the hood, I'm a bit lost as to where to go next for a fix.
I note that the Activestate examples are using IO::Socket rather than socket() directly and I further note that IO::Socket contains specifics for Win32, so that's where I'm inclined to think the problem lies.
Use of uninitialized value $sock in ref-to-glob cast at C:/Perl/site/l
+ib/Cache/Memcached.pm line 368.
Use of uninitialized value in vec at C:/Perl/site/lib/Cache/Memcached.
+pm line 368.
Use of uninitialized value $sock in ref-to-glob cast at C:/Perl/site/l
+ib/Cache/Memcached.pm line 375.
Use of uninitialized value in vec at C:/Perl/site/lib/Cache/Memcached.
+pm line 375.
Use of uninitialized value $sock in ref-to-glob cast at C:/Perl/site/l
+ib/Cache/Memcached.pm line 376.
send() on unopened socket at C:/Perl/site/lib/Cache/Memcached.pm line
+376.
Use of uninitialized value $res in numeric gt (>) at C:/Perl/site/lib/
+Cache/Memcached.pm line 379.
Use of uninitialized value $sock in hash element at C:/Perl/site/lib/C
+ache/Memcached.pm line 181.
Use of uninitialized value $sock in hash element at C:/Perl/site/lib/C
+ache/Memcached.pm line 168.
|