Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!swrinde!zaphod.mps.ohio-state.edu!uakari.primate.wisc.edu!aplcen!boingo.med.jhu.edu!haven!adm!smoke!gwyn
From: gwyn@smoke.brl.mil (Doug Gwyn)
Newsgroups: comp.lang.c
Subject: Re: realloc() (was: Re: Safe coding practices)
Message-ID: <15134@smoke.brl.mil>
Date: 8 Feb 91 20:55:52 GMT
References: <23975:Jan2516:36:5891@kramden.acf.nyu.edu> <1991Jan30.121425.16882@unhd.unh.edu> <00066@jimi.UUCP>
Organization: U.S. Army Ballistic Research Laboratory, APG, MD.
Lines: 6

In article <00066@jimi.UUCP> rob@jimi.UUCP writes:
>  Can anyone cite ANSI or any other reference to clear this up?

They've already done so.  realloc() is obliged, in a conforming
implementation, to preserve the old data (and validity of the
old pointer value) when it returns null.