Re: strncpy is not a safe version of strcpy

Поиск
Список
Период
Сортировка
От Kevin Grittner
Тема Re: strncpy is not a safe version of strcpy
Дата
Msg-id 1384528704.90487.YahooMailNeo@web162903.mail.bf1.yahoo.com
обсуждение исходный текст
Ответ на Re: strncpy is not a safe version of strcpy  (Alvaro Herrera <alvherre@2ndquadrant.com>)
Ответы Re: strncpy is not a safe version of strcpy  (Alvaro Herrera <alvherre@2ndquadrant.com>)
Список pgsql-hackers
Alvaro Herrera <alvherre@2ndquadrant.com> wrote:

> This code should probably be using namecpy().  Note namecpy()
> doesn't memset() after strncpy() and has survived the test of
> time, which strongly suggests that the memset is indeed
> superfluous.

That argument would be more persuasive if I could find any current
usage of the namecpy() function anywhere in the source code.

--
Kevin Grittner
EDB: http://www.enterprisedb.com
The Enterprise PostgreSQL Company



В списке pgsql-hackers по дате отправления:

Предыдущее
От: Rod Taylor
Дата:
Сообщение: Re: GIN improvements part2: fast scan
Следующее
От: Tom Lane
Дата:
Сообщение: Re: strncpy is not a safe version of strcpy