Re: get_progname() should not be const char *? - Mailing list pgsql-hackers

From Phil Sorber
Subject Re: get_progname() should not be const char *?
Date
Msg-id CADAkt-gGZTneCzbrnt9+umAfvDFtBGrNgnM8BicJOfMrE9EUVQ@mail.gmail.com
Whole thread Raw
In response to Re: get_progname() should not be const char *?  (Tom Lane <tgl@sss.pgh.pa.us>)
Responses Re: get_progname() should not be const char *?  (Robert Haas <robertmhaas@gmail.com>)
List pgsql-hackers
On Mon, Feb 4, 2013 at 10:52 PM, Tom Lane <tgl@sss.pgh.pa.us> wrote:
> Phil Sorber <phil@omniti.com> writes:
>> get_progname() returns a strdup()'d value. Shouldn't it then be simply
>> char * and not const char *? Otherwise free() complains loudly without
>> a cast.
>
> I don't believe that callers should be trying to free() the result.
> Whether it's been strdup'd or not is not any of their business.

Is that just because of the nature of this specific function?

>
>                         regards, tom lane



pgsql-hackers by date:

Previous
From: Tom Lane
Date:
Subject: Re: get_progname() should not be const char *?
Next
From: Pavel Stehule
Date:
Subject: Re: proposal: ANSI SQL 2011 syntax for named parameters