bug#24258: 25.1.50: In C++ `for' statement, second declaration is misfontified.

bug#24258: 25.1.50: In C++ `for' statement, second declaration is misfontified.

[Alan Mackenzie]

Hello, Emacs.

In C++ Mode, in the following:

    for (int32 a = 0, int32 b = 0; ; ) {
    }

, the second "int32" is getting font-lock-variable-name-face and "b" is
left unfontified.  This is a bug.

This was reported by Arash <pbqbqp@gmail.com>.

-- 
Alan Mackenzie (Nuremberg, Germany).

bug#24258: 25.1.50: In C++ `for' statement, second declaration is misfontified.

[Alan Mackenzie]

Hello, Arash.

On Thu, Aug 18, 2016 at 09:04:15AM +0000, Alan Mackenzie wrote:
> In C++ Mode, in the following:

>     for (int32 a = 0, int32 b = 0; ; ) {
>     }

> , the second "int32" is getting font-lock-variable-name-face and "b" is
> left unfontified.  This is a bug.

I'm not convinced that the above is correct syntax; the following, I
think, would be correct:

    for (int32 a = 0, b = 0 ; ... ; ...) { ... }

, but I don't think a second type (before the "b") is allowed.  I've
even tried it out with a compiler.

If this is the case, then CC Mode is behaving reasonably in fontifying
the second "int32" as a variable - it draws the programmer's attention
to something being wrong.

-- 
Alan Mackenzie (Nuremberg, Germany).

bug#24258: 25.1.50: In C++ `for' statement, second declaration is misfontified.

[Arash]

Oops lol, Sorry!
I was thinking of where else could something like
bug#24246 happen, I stopped thinking too early..

bug#24258: 25.1.50: In C++ `for' statement, second declaration is misfontified.

[Alan Mackenzie]

tags 24258 notabug
quit

Hello, Arash.

On Thu, Aug 18, 2016 at 04:13:36PM +0430, Arash wrote:
> Oops lol, Sorry!

No problem!

> I was thinking of where else could something like
> bug#24246 happen, I stopped thinking too early..

Thanks!  That's always a good thing to do with a bug.

And I learned something about for statements.

I'm closing this now as it's "not a bug".

-- 
Alan Mackenzie (Nuremberg, Germany).