On 3/12/2010 5:21 AM, Greg Stein wrote:
>
> It is *totally* fine to add a 'const' to a parameter that was not
> there before. That does not change the ABI whatsoever, and it will not
> break the API for callers. It merely gives them more information at
> compile time.
int oldfunc (const char *result);
int brokefunc ()
{
char *res = oldfunc();
}
doesn't compile on a single platform I know of.
Your statement makes no sense; how does adding const'ness to char *result
not come with source code level compatibility breakage?
