Path: utzoo!utgpu!jarvis.csri.toronto.edu!cs.utexas.edu!usc!snorkelwacker!bloom-beacon!EXPO.LCS.MIT.EDU!kit
From: kit@EXPO.LCS.MIT.EDU (Chris D. Peterson)
Newsgroups: comp.windows.x
Subject: Re: R4 Athena Widget question.
Message-ID: <9002261658.AA28416@expo.lcs.mit.edu>
Date: 26 Feb 90 16:58:00 GMT
References: <1990Feb24.002324.14813@agate.berkeley.edu>
Sender: daemon@athena.mit.edu (Mr Background)
Organization: The Internet
Lines: 29


> Exit(w, call, client)
>    Widget w;
>    caddr_t call, client;
>   {
>    XtDestroyApplicationContext(app_con);
>    exit(0);
>    }

> Now, from my own trauma with my application I have found that this will NOT
> call ANY of the widget's destroyCallback procedures. I now understand why
> (thanks to Paul Asente: asente@decwrl.dec.com). Now, many of the athena
> widgets do indeed have destroy callbacks, so it would seem that any
> application that exits in the above fashion is "doing the wrong thing".
> Would you (Consortium Staff), say this is true?


Since both the operating system and the X server are clever enough to free
up all resources associated with the client, it should be enough to just call
exit().  You can certainly be more clever, but it didn't seem worth putting a
bunch of code that doesn't accomplish anything into all the example programs.


						Chris D. Peterson     
						MIT X Consortium 

Net:	 kit@expo.lcs.mit.edu
Phone:   (617) 253 - 9608	
Address: MIT - Room NE43-213