Re: Code-Cleanup: char* -> const char*

From: Neil Conway <neilc(at)samurai(dot)com>
To: Stefan Huehner <stefan(at)huehner(dot)org>
Cc: pgsql-patches(at)postgresql(dot)org
Subject: Re: Code-Cleanup: char* -> const char*
Date: 2007-03-18 05:31:39
Message-ID: 45FCCEBB.4050102@samurai.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-patches

Stefan Huehner wrote:
> attached patches marks several char* variables as const where they are
> initialized with constant strings.
>

I really wonder how much value there is in using the "const" modifier
very widely. "const" for function parameters is valuable (because it
adds information about the function's behavior to its interface). It
also makes sense to use "const" on global variables, when it reduces the
size of the binary's data segment. Beyond that, you reach the point of
diminishing returns fairly quickly, IMHO. (In C, anyway; it makes more
sense to use it widely in C++, of course.)

I also don't see the value in modifying the regexp code, as that is just
an import of Henry Spencer's regexp package. I'm not sure whether we're
planning on merging any upstream changes any time soon, but making
cosmetic changes to the RE code will only make that more difficult.

Anyway, I'll apply this tomorrow without the RE changes, barring any
objections.

BTW, the preferred format for patches is context diffs, not unified diffs.

-Neil

In response to

Responses

Browse pgsql-patches by date

  From Date Subject
Next Message Neil Conway 2007-03-18 05:37:32 Re: Code-Cleanup: function declarations (void, and k&r style)
Previous Message Magnus Hagander 2007-03-17 22:18:01 ecpg threading vs win32