getopt() and strdup()
От
Bruce Momjian
Тема
getopt() and strdup()
Дата
Msg-id
20121008184026.GA28752@momjian.us
Список
Дерево обсуждения
getopt() and strdup() Bruce Momjian <bruce@momjian.us>
Re: getopt() and strdup() Tom Lane <tgl@sss.pgh.pa.us>
Re: getopt() and strdup() Bruce Momjian <bruce@momjian.us>
Re: getopt() and strdup() Bruce Momjian <bruce@momjian.us>
Re: getopt() and strdup() Bruce Momjian <bruce@momjian.us>
Re: getopt() and strdup() Phil Sorber <phil@omniti.com>
Re: getopt() and strdup() Tom Lane <tgl@sss.pgh.pa.us>
Re: getopt() and strdup() Phil Sorber <phil@omniti.com>
Re: getopt() and strdup() Andrew Dunstan <andrew@dunslane.net>
A while ago I noticed that in some places we strdup/pg_strdup() optarg strings from getopt(), and in some places we don't. If we needed the strdup(), the missing cases should generate errors. If we don't need them, the strdup() is unnecessary, and research confirms they are unnecessary. Should we remove the extra strdup/pg_strdup() calls, for consistency. I think we might have had old platforms that required it, but none are still supported today. -- Bruce Momjian http://momjian.us EnterpriseDB http://enterprisedb.com + It's impossible for everything to be true. +
В списке pgsql-hackers по дате отправления
