Added more test cases.  All of the new test cases compile and run, and are resolvable by the editor.  Only the "auto" declaration in the range based for loop is unresolvable by the editor.

#include <iostream>
#include <vector>

using namespace std;

struct A
{
    void SomeMemberFunction()
    {
        cout << "Hello\n";
    }
};


int main()
{
    vector<A*> vector_of_ptrs_to_A;
    vector_of_ptrs_to_A.push_back( new A() );
    
    for ( auto& e : vector_of_ptrs_to_A )
    {
        //"Unable to resolve identifier SomeMemberFunction."
        e->SomeMemberFunction();
    }
    
    for ( A*& e : vector_of_ptrs_to_A )
    {
        e->SomeMemberFunction(); //Netbeans can resolve this just fine.
    }
    
    for ( A* e : vector_of_ptrs_to_A )
    {
        e->SomeMemberFunction(); //Netbeans can resolve this just fine.
    }
    
    for ( decltype( vector_of_ptrs_to_A )::value_type& e : vector_of_ptrs_to_A )
    {
        e->SomeMemberFunction(); //Netbeans can resolve this just fine.
    }

    auto& elem = vector_of_ptrs_to_A.front();
    elem->SomeMemberFunction();
}

What is your compiler? Seems to be related with compiler stl, because with gcc 6.2.0 and gcc 5.3.0 it works fine.

Created attachment 163365 [details]
screenshot - red underline

Created attachment 163366 [details]
screenshot - "Unable to resolve identifier" popup

(In reply to petrk from comment #2)
> What is your compiler? Seems to be related with compiler stl, because with
> gcc 6.2.0 and gcc 5.3.0 it works fine.

$ gcc --version
gcc (Ubuntu 5.4.0-6ubuntu1~16.04.4) 5.4.0 20160609
Copyright (C) 2015 Free Software Foundation, Inc.
This is free software; see the source for copying conditions.  There is NO
warranty; not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.

---

Just to reiterate, I'm able to compile and run just fine. The error is in the editor/code assistance.  Please see attached screenshots.

> Just to reiterate, I'm able to compile and run just fine. The error is in the editor/code assistance.  Please see attached screenshots.

Yes, I'm just saying that NetBeans has troubles parsing stl files of particular version, 5.4 in this case. By the way, are you sure that your project is configured properly? I mean the standard is set to C++11 or C++14. Can you please attach the sample project here?

Created attachment 163369 [details]
sample project

(In reply to petrk from comment #6)
> > Just to reiterate, I'm able to compile and run just fine. The error is in the editor/code assistance.  Please see attached screenshots.
> 
> Yes, I'm just saying that NetBeans has troubles parsing stl files of
> particular version, 5.4 in this case. By the way, are you sure that your
> project is configured properly? I mean the standard is set to C++11 or
> C++14. Can you please attach the sample project here?

Under "Project Properties" -> "Build" -> "C++ Compiler" -> "Basic Options", C++ Standard is set to C++14.

The sample project is attached.

Hi, 

Cannot reproduce the bug, even with headers from gcc 5.4. Can you please extract somehow the part which prevents "auto" from being resolved? Or at least attach preprocessed file here (using -E option)?

(In reply to petrk from comment #8)
> Hi, 
> 
> Cannot reproduce the bug, even with headers from gcc 5.4. Can you please
> extract somehow the part which prevents "auto" from being resolved? Or at
> least attach preprocessed file here (using -E option)?

I started with a clean install of Netbeans 8.2 to try to reproduce the bug, and at first I was unable to reproduce it.

Unable to reproduce the bug:
At first, I only had the attached sample project opened (see attachments at the top of this bug report page).  With just that project open in Netbeans, if I right click on the project -> Code Assistance -> Reparse Project, then while the project is in the process of being re-parsed, I do notice that the red underline appears, as shown in the screenshot (see first attachment at the top of this bug report page).  However, just before the parsing process completes (i.e. the progress bar at the bottom right of the Netbeans window is almost at 100%), the red underline disappears, and the auto variable in the range based for loop seems to be successfully resolved.  So it seems like resolving that auto variable happens near the end of the parsing process.

Able to reproduce the bug:
However, I was then able to recreate the bug by opening another particular large C++ project that I'm working on, in addition to the attached sample project.  With both projects open, when I again try to re-parse the attached sample project, it starts out doing the same thing in that the red underline appears during parsing, but this time, when the parsing finishes, the red underline doesn't disappear, and Netbeans is unable to resolve the auto variable in the range based for loop.  If I then close that large project, and again re-parse the sample project, then the red underline does disappear as described above (under "Unable to reproduce the bug:"), and the auto variable in the range based for loop gets successfully parsed.

I can't attach that large C++ project because #1 it's big, and #2 it's a project for work.  There seems to be something about having that large project open that prevents the IDE from successfully parsing and resolving auto variables in range based for loops, but I don't know what that 'something' is yet.

I've just discovered that the bug can be reproduced by creating any new C++ project (C++ application) in Netbeans.  So if I have two projects open in Netbeans, where one project is the sample project, and the other project is the new default C++ project, when I re-parse the sample project, I see the bug.