Re: [cdt-dev] code completion & C++11

[scalpel4k <scalpel4k@xxxxxxxxx>]

Hi Thomas,

I just opened this bug: https://bugs.eclipse.org/bugs/show_bug.cgi?id=400309

I put it under the indexer category, maybe that's wrong.

And thanks for the quick response. I hope the solution will be just as quick ;-)

bye Michi

On Friday 08 Feb 2013 10:42:11 Corbat Thomas wrote:
> Hi Michi
> 
> Thanks for the report. I can confirm the behavior you are observing regarding code completion. Without further investigation I would guess that the allowed completion of the private and protected nested classes inside a class has been possible even before C++11 in CDT. According to [class.access.nest] in the former standard this had been denied explicitly, unlike access to other members.
> 
> CDT should not offer inaccessible members for completion. When you issue a bug, I'll look into the completion of inaccessible members from outside.
> 
> Apart from that, is there a general policy about how CDT reacts when the expected behavior of different standards is contradicting? Like the access to other nested classes as in the attached example?
> 
> Regards
> Thomas
> 
> 
> 
> -----Original Message-----
> From: cdt-dev-bounces@xxxxxxxxxxx [mailto:cdt-dev-bounces@xxxxxxxxxxx] On Behalf Of scalpel4k
> Sent: Freitag, 8. Februar 2013 10:31
> To: cdt-dev@xxxxxxxxxxx
> Subject: [cdt-dev] code completion & C++11
> 
> Hi guys,
> 
> I have some issues with code completion in C++ and nested classes, and I guess it has to do with C++11. The latter has changed how nested classes have access to private/protected declarations in the nesting class.
> 
> I have attached a test case that produces some weird results. Before I issue a bug report I wanted to know whether I'm just too stupid to get things right.
> 
> bye Michi
> _______________________________________________
> cdt-dev mailing list
> cdt-dev@xxxxxxxxxxx
> https://dev.eclipse.org/mailman/listinfo/cdt-dev