Code::Blocks Forums
User forums => General (but related to Code::Blocks) => Topic started by: killerbot on April 13, 2015, 04:07:59 pm
-
the keyword "override" is no longer coloured.
Could be this problem is present for some time, today updated a pc to trunk (last time that one was updated was months ago) , back then override was nicely "blue" coloured.
-
Check the c++ lexer related files. Probably someone has removed it from one of the keywords lists.
-
Probably someone has removed it from one of the keywords lists.
Its not there. I also can't remember that is has been there at all. Maybe you did it manually within C::B (changing/extending the lexer keywords I mean)?
-
I still have a system on rev 10053 (24 dec 2014), and there the override keyword is still nicely blue coloured.
-
Ok, then you know what to do... :-)
-
Yes, i do. i Will be back ...
-
http://sourceforge.net/p/codeblocks/code/10132/
-
Thanks, @thomas, what was the rationale of kicking 'final, override' out of the list ?
-
Unintentional, please feel free to re-add these!
I first added noexcept because it was really annoying that this one wasn't highlighted. Doing that, I stumbled over the obsolete N2018 types and corrected these to the final standard ones, and promptly detected the obsolete proposal align_union which I removed.
Then I said to myself, well, that is all nice and good, but there's already so many things, let's make sure no other mistake has creeped in.
So I tossed it all overboard and took the complete list of valid keywords (including one reserved keyword) from the standard. This is where override and final got unintentionally dropped. Happens that they aren't keywords at all, but obviously one would want to color them as such anyway. Sorry about that.
-
They're context-aware-keywords or something like this.
This is done in order to not break code which uses override/final for identifier/function names. :)
-
fixed on trunk