Path: utzoo!utgpu!jarvis.csri.toronto.edu!mailrus!csd4.csd.uwm.edu!cs.utexas.edu!uunet!mcsun!hp4nl!targon!andre
From: andre@targon.UUCP (andre)
Newsgroups: comp.lang.c
Subject: Re: What happens when realloc() returns NULL?
Message-ID: <620@targon.UUCP>
Date: 1 Sep 89 11:22:03 GMT
References: <TOM.89Aug30231415@yang.cpac.washington.edu>
Reply-To: andre@targon.UUCP (andre)
Organization: Nixdorf Computer BV., DO, P.O. Box 29,Vianen, The Netherlands
Lines: 12

In article <TOM.89Aug30231415@yang.cpac.washington.edu> tom@yang.cpac.washington.edu (Tom May) writes:

>and malloc() returns non-NULL, but realloc() returns NULL, is the memory
>pointed to by p1 still allocated?

Yes, it is or nobody would use realloc anymore... :-)

-- 
    \---|    AAA         DDDD  It's not the kill, but the thrill of the chase.
     \  |   AA AAvv   vvDD  DD        Ketchup is a vegetable.
  /\  \ |  AAAAAAAvv vvDD  DD                    {nixbur|nixtor}!adalen.via
_/__\__\| AAA   AAAvvvDDDDDD    Andre van Dalen, uunet!hp4nl!targon!andre