Path: utzoo!news-server.csri.toronto.edu!cs.utexas.edu!sun-barr!newstop!texsun!convex!usenet From: tchrist@convex.COM (Tom Christiansen) Newsgroups: comp.lang.perl Subject: Re: Default actions for %SIG Message-ID: <1991Mar07.220845.3888@convex.com> Date: 7 Mar 91 22:08:45 GMT References: <11683@jpl-devvax.JPL.NASA.GOV> <124822@uunet.UU.NET> Sender: usenet@convex.com (news access account) Reply-To: tchrist@convex.COM (Tom Christiansen) Distribution: comp Organization: CONVEX Software Development, Richardson, TX Lines: 20 Nntp-Posting-Host: pixel.convex.com From the keyboard of victor@ibm.com: :When I set up a @SIG{'PIPE'} handler, all it could do is report that :there was a PIPE error, but couldn't tell me where. You mean a _$SIG{'HANDLER'}. The caller seems set up to do nearly this, but unfortunately it doesn't work in signal handlers as it does in other functions. The way I set up my pipe handlers, it hasn't ever been ambiguous what was going on. Could you show an example of this? Maybe it's time to repost my "how to handle pipes to/from programs that might now be there" stuff. --tom -- I get so tired of utilities with arbitrary, undocumented, compiled-in limits. Don't you? Tom Christiansen tchrist@convex.com convex!tchrist