Bug 277607 - using namespace directive not fully handled.
Summary: using namespace directive not fully handled.
Status: RESOLVED FIXED
Alias: None
Product: kdevelop
Classification: Applications
Component: Language Support: CPP (old) (show other bugs)
Version: git master
Platform: Compiled Sources Linux
: NOR normal
Target Milestone: ---
Assignee: kdevelop-bugs-null
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2011-07-12 09:33 UTC by cedric
Modified: 2021-03-10 09:52 UTC (History)
0 users

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

Attachments
file not correctly parsed by kdevelop at line 20 (272 bytes, application/x-download)
2011-07-13 13:55 UTC, cedric 		Details
View All Add an attachment

Note You need to log in before you can comment on or make changes to this bug.
Description cedric 2011-07-12 09:33:24 UTC 
Version:           git master (using Devel) 
OS:                Linux

when "using namespace Foo;" is used within a namespace Bar, each following namespace Bar scope should know about namespace Foo.
In the attached an exemple of code, line 20, class AA is not solved by the code analyser but the code is valid (it compile with g++ at least from g++ 3.4 and with ms compiler at least with version 2005)

Reproducible: Always

Steps to Reproduce:
Open the attached file with kdevelop, line 20, class AA is not recognized.


Expected Results:  
In the attached file, line 20, class AA should have been resolved as A::AA
Comment 1 Milian Wolff 2011-07-12 10:24:22 UTC 
you forgot the file attachement
Comment 2 cedric 2011-07-13 13:55:33 UTC 
Created attachment 61845 [details]
file not correctly parsed by kdevelop at line 20
Comment 3 Milian Wolff 2011-07-13 14:22:51 UTC 
confirmed
Comment 4 Justin Zobel 2021-03-09 22:48:34 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 cedric 2021-03-10 09:52:54 UTC 
The issue is no longer present.
thanks :)