Re: Reasons not to like asprintf
От | Peter Eisentraut |
---|---|
Тема | Re: Reasons not to like asprintf |
Дата | |
Msg-id | 5269645A.9050609@gmx.net обсуждение исходный текст |
Ответ на | Re: Reasons not to like asprintf (Tom Lane <tgl@sss.pgh.pa.us>) |
Ответы |
Re: Reasons not to like asprintf
Re: Reasons not to like asprintf |
Список | pgsql-hackers |
On 10/22/13, 3:40 PM, Tom Lane wrote: > In order to avoid having to clutter stuff like that with #ifdef FRONTENDs, > I'm now thinking we should use exactly the same names for the frontend and > backend versions, ie psprintf() and pvsprintf(). The main reason for > considering a pg_ prefix for the frontend versions was to avoid cluttering > application namespace; but it's already the case that we don't expect > libpgcommon to be namespace clean. While this is attractive, the same logic would suggest that we rename pg_malloc() to palloc(), and that sounds wrong. The frontend and backend functions do have different freeing semantics.
В списке pgsql-hackers по дате отправления: