>> With glibc, if p is not null, realloc (p, 0) always returns NULL.
>
> And free's p, presumably?

Yes.

> The glibc behaviour here seems like something we shouldn't encourage
> IMHO.

Ah, then we probably shouldn't document it either.  (:-)


Reply via email to