Path: utzoo!utgpu!jarvis.csri.toronto.edu!clyde.concordia.ca!uunet!seismo!sundc!newstop!sun!turnpike!argv From: argv%turnpike@Sun.COM (Dan Heller) Newsgroups: comp.windows.x Subject: Re: Problem with Signals Message-ID: <132495@sun.Eng.Sun.COM> Date: 4 Mar 90 03:07:41 GMT References: <9002281729.AA02895@wilkins.bcm.tmc.edu> <132399@sun.Eng.Sun.COM> <4429@quanta.eng.ohio-state.edu> <132493@sun.Eng.Sun.COM> Sender: news@sun.Eng.Sun.COM Reply-To: argv@sun.UUCP (Dan Heller) Lines: 47 Geez, not only did I forget to proofread my last message, I forgot to *finish* it before I posted it.. It's been a very long week.... My previous message was supposed to look like this: In article <4429@quanta.eng.ohio-state.edu> JONESD@kcgl1.eng.ohio-state.edu (David Jones) writes: > Instead of hacking up tookits to allow your application to add signal handlers, > I'd rather see them hacked up to convert signals into client events. The > application would deal with with the signal as another event to deal and > not as something to be dealt with by a signal handler. That's fundamentally the same thing I'm talking about. That is, you should register signals and handlers (functions) for those signals with a toolkit or its intrinsics (Xt, in this case). The toolkit calls the function registered for the signal in case one is delivered. However, the idea about converting signals into events doesn't make sense -- signals don't happen in windows [%] and they don't have any of the associated values that accompany existing X events such as a serial #, window ID, x/y values, etc... Signals are associated with processes, not X clients. The problem may become more complicated as subprocesses are created (fork(), for example). [%] SIGWINCH is a possible exception and an interesting case.. altho not that interesting... From: PARCEL@INTELLICORP.COM (Scott Parcel) Subject: X & Signals Message-ID: <9002281442.aa11275@mintaka.lcs.mit.edu> Date: 28 Feb 90 19:37:02 GMT I have some questions and comments about the recent discussion of handling events inside of Unix signal handlers. My particular interest is in using signals to do all X event processing. Can you please explain this? This makes no sense to me. What kind of interface do you provide for an application that does nothing but trap signals? What kind of functionality does such an application serve? dan ----------------------------------------------------------- O'Reilly && Associates argv@sun.com / argv@ora.com 632 Petaluma Ave, Sebastopol, CA 95472 800-338-NUTS, in CA: 800-533-NUTS, FAX 707-829-0104 Opinions expressed reflect those of the author only.