"Bruce Momjian" <[EMAIL PROTECTED]> wrote: > Gaetano Mendola wrote: > > "Bruce Momjian" <[EMAIL PROTECTED]> wrote: > > > I see other strdup() calls that don't check on a return. Should we deal > > > with those too? > > > > Well strdup obtain the memory for the new string using a malloc > > and normally is a good habit check the return value of a malloc. > > Right. My point is that we have lots of other strdup's in the code. > Should we fix those too? Seems we should be consistent.
Of course yes, consider also that inside SetVariable the check is performed but too late, after that the old value was loose for ever. Keep also the suggestion of Tom Late about the xstrdup. Regards Gaetano Mendola ---------------------------(end of broadcast)--------------------------- TIP 4: Don't 'kill -9' the postmaster
