Bug 318767 - strings and chars no longer work in preprocessed c++ macro
Summary: strings and chars no longer work in preprocessed c++ macro
Status: RESOLVED WORKSFORME
Alias: None
Product: kdevelop
Classification: Applications
Component: Language Support: CPP (old) (show other bugs)
Version: git master
Platform: Gentoo Packages Linux
: NOR normal
Target Milestone: ---
Assignee: kdevelop-bugs-null
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2013-04-23 13:39 UTC by Bernd Buschinski
Modified: 2023-02-01 05:05 UTC (History)
1 user (show)

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


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Bernd Buschinski 2013-04-23 13:39:36 UTC
This seems to be a regression as it used to work with older versions.

Reproducible: Always

Steps to Reproduce:
1. Using the given c++ code
#define Doit(x) x

    Doit("x");
    Doit('x');
    Doit(1);
    Doit(asd);

2. hover the mouse over     Doit("x"); or     Doit('x');
Actual Results:  
the Code Browser shows preprocessed body: (empty)

Expected Results:  
should be "x", or 'x', but not empty

using kdevplatform kdevelop (&kdevelop-python) git master
Hovering over Doit(1); and Doit(asd); still works and shows 1 and asd, so numbers and strings (without ' or ") still works.
Comment 1 Andrew Crouthamel 2018-11-11 04:35:04 UTC
Dear Bug Submitter,

This bug has been stagnant for a long time. Could you help us out and re-test if the bug is valid in the latest version? I am setting the status to NEEDSINFO pending your response, please change the Status back to REPORTED when you respond.

Thank you for helping us make KDE software even better for everyone!
Comment 2 Bernd Buschinski 2018-11-15 21:10:44 UTC
It seems this feature got lost in kdevelop5 completely?
I only see
"Body: x"
now.

Or is there some way to activate it?
Comment 3 Kevin Funk 2018-11-16 06:52:45 UTC
Yes, that was never implemented. It's hard if not impossible to get the preprocessed macro output from libclang, at least at the time I was trying to implement that (a couple years ago).
Comment 4 Andrew Crouthamel 2018-11-21 04:15:11 UTC
Do you want to leave this open?
Comment 5 Justin Zobel 2023-01-02 07:43:46 UTC
Thank you for reporting this issue in KDE software. As it has been a while since this issue was reported, can we please ask you to see if you can reproduce the issue with a recent software version?

If you can reproduce the issue, please change the status to "REPORTED" when replying. Thank you!
Comment 6 Bug Janitor Service 2023-01-17 05:15:43 UTC
Dear Bug Submitter,

This bug has been in NEEDSINFO status with no change for at least
15 days. Please provide the requested information as soon as
possible and set the bug status as REPORTED. Due to regular bug
tracker maintenance, if the bug is still in NEEDSINFO status with
no change in 30 days the bug will be closed as RESOLVED > WORKSFORME
due to lack of needed information.

For more information about our bug triaging procedures please read the
wiki located here:
https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging

If you have already provided the requested information, please
mark the bug as REPORTED so that the KDE team knows that the bug is
ready to be confirmed.

Thank you for helping us make KDE software even better for everyone!
Comment 7 Bug Janitor Service 2023-02-01 05:05:10 UTC
This bug has been in NEEDSINFO status with no change for at least
30 days. The bug is now closed as RESOLVED > WORKSFORME
due to lack of needed information.

For more information about our bug triaging procedures please read the
wiki located here:
https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging

Thank you for helping us make KDE software even better for everyone!