Graham Barr didn't seem to understand that errors for "system-related" operations
should be returned by setting $! to something sane, and instead
put the error text in $@, which is reserved for eval errors.
No amount of pleading with him has seemed to convince him that he needs
to set the appropriate value.
So try looking in $@ instead of $! when you get an IO::Socket::mumble error.
-- Randal L. Schwartz, Perl hacker | [reply] |
Thanks for your reply
I solved the problem eventually. I had hardcoded the computer name
address in the server program and used the hostname() method
in the client program. Even though both programs sat on
the same computer, the client could not figure out where to
send the data to.
All this became a little clearer when I put in the -w switch
in at the top. But i have now inserted $@ instead of $i in the code.
many thanks
Ant
| [reply] |