Path: utzoo!news-server.csri.toronto.edu!cs.utexas.edu!uunet!bywater!arnor!arnor!victor From: victor@arnor.UUCP (Victor Miller) Newsgroups: comp.lang.perl Subject: Re: Default actions for %SIG Message-ID: Date: 7 Mar 91 15:29:40 GMT References: <11683@jpl-devvax.JPL.NASA.GOV> <124822@uunet.UU.NET> Sender: news@arnor.uucp (NNTP News Poster) Reply-To: victor@ibm.com Distribution: comp Organization: IBM, T.J. Watson Research Center Lines: 30 In-Reply-To: rbj@uunet.UU.NET's message of 6 Mar 91 21:27:21 GMT >>>>> On 6 Mar 91 21:27:21 GMT, rbj@uunet.UU.NET (Root Boy Jim) said: rbj> lwall@jpl-devvax.JPL.NASA.GOV (Larry Wall) writes: rbj> ?In article victor@ibm.com writes: rbj> ?: Where is there a list of the default actions for %SIG? I couldn't rbj> ?: find it either in "Programming Perl" or in the man page. rbj> ? rbj> ?That's somewhat OS dependent. Try "man 2 signal", or maybe "man 3 signal". rbj> Yes, but we need more signal support. I would like to block rbj> signals, set masks, etc. Either POSIX or 4.3 interface would be fine. rbj> Actually, it should probably be POSIX. At least say "someday". rbj> -- rbj> [rbj@uunet 1] stty sane rbj> unknown mode: sane I agree. As an addition is it at all possible (I suspect it's hard) to have signals give some kind of indication of what line in the perl program they interrupted. For some internal signals (such as PIPE) this might be possible. For example, I had done something stupid so when I tried to write to a filehandle which was a pipe to a non-existent program, the perl script just quit silently (actually not completely -- there was some sort of mysterious status code set). 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. -- Victor S. Miller Vnet and Bitnet: VICTOR at WATSON Internet: victor@ibm.com IBM, TJ Watson Research Center