At 04:08 PM 2/8/2001 -0500, Charles Bailey wrote:
>| At 10:46 AM 2/8/2001 -0600, Forrest Cahoon wrote:
>| >I'm sorry this message is so long, but we are having some real trouble
>| >using sockets from perl here, and I desperately want to get to the
>| >bottom of it. It appears that perl programs using sockets on our
>| >OpenVMS system immediately echo back any messages they receive.
>| | You can't use C's stdio calls on sockets on VMS. (Which means no print
>or | <>) If you need to read or write to them, use sysread and syswrite.
>
>I just added to the repository a patch which converts prints() to sockets
>into write()s under the hood; it may halp you out here. Haven't had
>problems with <> on sockets (other than hanging), so I can't add much
>there (not that I've tested it extensively).
<> sort of works, but I wouldn't rely on it. Since the behaviour's
undefined, it may (probably will) change occasionally. Hopefully the
changes will be for the better, but until things are declared to work, I
wouldn't use it if I could avoid it.
Dan
--------------------------------------"it's like this"-------------------
Dan Sugalski even samurai
[EMAIL PROTECTED] have teddy bears and even
teddy bears get drunk
