"Tom Lane" <tgl@sss.pgh.pa.us> wrote:
> Bruce Momjian <pgman@candle.pha.pa.us> writes:
> > I see other strdup() calls that don't check on a return. Should we deal
> > with those too?
>
> strdup -> xstrdup if you're concerned.
May be is a good idea avoid the future use:
#define strdup STRDUP_DEPRECATED_USE_INSTEAD_XSTRDUP
I don't like the other solution: redefine the strdup in function of xstrdup.
Regards
Gaetano Mendola