Bug 269784 - Syntax coloring mixup. __LINE__ breaks C++ ranges
Summary: Syntax coloring mixup. __LINE__ breaks C++ ranges
Status: RESOLVED FIXED
Alias: None
Product: kdevelop
Classification: Applications
Component: Language Support: CPP (old) (other bugs)
Version First Reported In: git master
Platform: Compiled Sources Linux
: NOR minor
Target Milestone: ---
Assignee: kdevelop-bugs-null
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2011-03-30 21:33 UTC by Lambert Clara
Modified: 2025-11-10 10:35 UTC (History)
1 user (show)

See Also:
Latest Commit:
Version Fixed/Implemented In:
Sentry Crash Report:

Attachments
Cpp file showing the problem. (96 bytes, text/x-c++src)
2011-03-30 21:36 UTC, Lambert Clara 		Details
View All Add an attachment

Note You need to log in before you can comment on or make changes to this bug.
Description Lambert Clara 2011-03-30 21:33:37 UTC 
Version:           git master (using KDE 4.6.1) 
OS:                Linux

A simple text "test " is treated part as text and part as hoverable object.

Reproducible: Always

Steps to Reproduce:
Load the attached file into kdevelop, wait for the syntax coloring.

Actual Results:  
The first two letters in "test " are have a different color than the rest of the word, and if I hover them it displays a frame with the QDebug operator << description.

Expected Results:  
The "test " word should have been marked as a text and not be hoverable.
Comment 1 Lambert Clara 2011-03-30 21:36:41 UTC 
Created attachment 58468 [details]
Cpp file showing the problem.
Comment 2 Aleix Pol 2013-02-27 23:33:44 UTC 
I still could reproduce, I guess it's __FILE__ not being preprocessed properly.
Comment 3 Aleix Pol 2013-02-27 23:37:34 UTC 
(In reply to comment #2)
> I still could reproduce, I guess it's __FILE__ not being preprocessed
> properly.

Not __FILE__ but __LINE__.

I actually tested and __FILE__ works
Comment 4 Justin Zobel 2021-03-09 22:48:06 UTC 
Thank you for the bug report.

As this report hasn't seen any changes in 5 years or more, we ask if you can please confirm that the issue still persists.

If this bug is no longer persisting or relevant please change the status to resolved.
Comment 5 Lambert Clara 2025-11-10 10:35:33 UTC 
Tested with version 6.3.250802 (25.08.2), and bug doesn't repro, closing as fixed!