On Wed, 07 May 2014 02:13:10 +
"Bryce W. Harrington" wrote:
> As per our discussion last week, here's patches to convert client code
> to using xmalloc, xzalloc, xcalloc, and xstrdup where appropriate.
>
> I opted not to change nested.c, because it looked like errors were
> being propagated
As per our discussion last week, here's patches to convert client code
to using xmalloc, xzalloc, xcalloc, and xstrdup where appropriate.
I opted not to change nested.c, because it looked like errors were being
propagated to a higher level for handling, and bombing out on OOM might
not be desired?
