GNU bug report logs - #24246
25.0.95; (c++-mode) custom/extra types not getting highlighted (as a type) after a wrapper::type argument.

Previous Next

Packages: cc-mode, emacs;

Reported by: Arash <pbqbqp <at> gmail.com>

Date: Tue, 16 Aug 2016 20:55:02 UTC

Severity: minor

Found in version 25.0.95

Done: Alan Mackenzie <acm <at> muc.de>

Bug is archived. No further changes may be made.

Full log


View this message in rfc822 format

From: Michael Welsh Duggan <mwd <at> md5i.com>
To: Arash <pbqbqp <at> gmail.com>
Cc: Alan Mackenzie <acm <at> muc.de>, 24246 <at> debbugs.gnu.org
Subject: bug#24246: 25.0.95; (c++-mode) custom/extra types not getting highlighted (as a type) after a wrapper::type argument.
Date: Tue, 23 Aug 2016 18:34:40 -0400
Arash <pbqbqp <at> gmail.com> writes:

> Thanks, fontification for function decs/defs got fixed but the problem
> still exists in e.g. init step of a for loop...
>
> for (wrapper::type a = 0, int32 b = 0; ; ) {
>     ...
> }

I don't believe that is legal C++.  The for-init-statement must be a
single statement.  Since "wrapper::type a = 0, int32 b = 0;" is not a
legal statement, it is not a legal for-init-statement.

The following, however, is legal:

  for (struct{wrapper::type a; int32 b;} var = {0, 0}; ; ) {
  
  }

-- 
Michael Welsh Duggan
(md5i <at> md5i.com)




This bug report was last modified 8 years and 310 days ago.

Previous Next


GNU bug tracking system
Copyright (C) 1999 Darren O. Benham, 1997,2003 nCipher Corporation Ltd, 1994-97 Ian Jackson.