Path: utzoo!attcan!uunet!seismo!ukma!tut.cis.ohio-state.edu!snorkelwacker!bloom-beacon!EXPO.LCS.MIT.EDU!rws
From: rws@EXPO.LCS.MIT.EDU (Bob Scheifler)
Newsgroups: comp.windows.x
Subject: Re: Returning from XtMalloc??
Message-ID: <9003011404.AA00236@expire.lcs.mit.edu>
Date: 1 Mar 90 14:04:56 GMT
References: <9002271554.AA12993@ra.>
Sender: daemon@athena.mit.edu (Mr Background)
Organization: The Internet
Lines: 19


    The X Toolkit Intrinsics manual (X11R3) says "These functions
    [XtMalloc, XtCalloc, XtRealloc] are completely compatible with their C
    language runtime counterparts ..."

But it explicitly goes on to say "with the following added functionality"
and explains that out-of-memory produces an error, and the description
of XtError explicitly says that it invokes XtErrorMsg in this case.

    Does this mean one should use the Xt alloc functions only
    when the memory they grab is strictly necessary to continue with
    client execution?

Yes.

    Should we use regular C alloc functions when there
    is the possibility of continueing from a failed alloc?

Sure.