At 10:32 AM -0500 1/14/05, Thomas R Wyant_III wrote: >The PERLIO environment variable is not defined on the system, and I >haven't put any "use open" pragmas in the script. The actual "open" is >accounted for. The perlipc doc says this means :perlio for 5.8.4, but it >also seems to say that I should get my signals delivered if :perlio is in >use. Or am I reading it wrong? Perlrun says the default is :stdio, but I >guess I would expect perlipc to rule in this case.
The way to find out what you're configured with is: $ perl -"V:useperlio" useperlio='define'; Yes, perlio is now the default, and as far as I can see perlrun says so too. What might have confused you in perlrun is that the default implementation of the perlio layering capability is based on the native C library's stdio facilities. I read the perlipc documentation the same way you do, i.e., the signal should get delivered when using perlio. But we could have a bug or an implementation-defined behavior or a loophole closed for stability reasons but not documented properly. This would need to be tested and compared on various platforms before filing a bug report I think. -- ________________________________________ Craig A. Berry mailto:[EMAIL PROTECTED] "... getting out of a sonnet is much more difficult than getting in." Brad Leithauser
