Re: Emacs rewrite in a maintainable language

[Sergey Organov]

Oleh Krehel <address@hidden> writes:

> Alan Mackenzie <address@hidden> writes:
>
>> Hello, Oleh.
>>
>> On Tue, Oct 13, 2015 at 01:27:49PM +0200, Oleh Krehel wrote:
>>
>>> May I ask if there's a reason to not have a single style for const
>>> pointers? I get 2162 occurrences of "const char *", and 357 occurrences
>>> of "char const *" in the C sources.
>>
>> Yes there is.  The two are semantically different.  In one of them, it is
>> the pointer which is declared constant.  In the other, it's what's
>> pointed at that's constant.  Though I can never remember which is which.
>> :-(
>
> Hi Alan,
>
> Actually, "const char *" and "char const *" are absolutely equivalent in
> all regards, both in C and C++.
>
> I think you meant the difference between "const char *" and "char * const".
>
> For exactly this reason (the confusion over 3 notations, 2 of which are
> the same), I propose that we stick only to "const char *" and "char * const",
> and don't use "char const *".

People write "char const *" because it uses the general and simple rule
"'const' applies to what is to the left", that makes it easy to figure
what "char * const" means and why ('const' applies to '*' here, to
the pointer).

OTOH, "const char *", while looks more "natural", relies on additional
rule "when nothing is to the left, 'const' applies to what is to the
right".

Dunno if enforcing one form or another makes sense.

-- Sergey.