Path: utzoo!utgpu!news-server.csri.toronto.edu!mailrus!wuarchive!zaphod.mps.ohio-state.edu!usc!snorkelwacker!bloom-beacon!eru!hagbard!sunic!mcsun!ukc!axion!axion.bt.co.uk!crouch
From: crouch@axion.bt.co.uk (Chris Rouch)
Newsgroups: comp.windows.x
Subject: XtMalloc always fails fatally - why?
Message-ID: <1990Aug31.105145.22656@axion.bt.co.uk>
Date: 31 Aug 90 10:51:45 GMT
Sender: news@axion.bt.co.uk
Reply-To: CRouch@axion.bt.co.uk
Organization: British Telecom Research Labs
Lines: 15

Whenever XtMalloc fails to allocate memory it calls an error message
handler which calls exit, thus terminating the application. What is the
reason for doing it this way, rather than letting the calling procedure
decide what action to take? More importantly is there any way round
this?

Chris
------------------------------------------------------------------------
------
Chris Rouch                                            
crouch@axion.bt.co.uk
RT3131, BTRL, Martlesham Heath, Ipswich, England.              +44 473
646093

Only when we dream are we free. The rest of the time we need wages.