Re: Red Mark of Death or 'Unable to resolve identifier'

  • From: Leonid Lenyashin < >
  • To:
  • Subject: Re: Red Mark of Death or 'Unable to resolve identifier'
  • Date: Fri, 27 Jul 2012 12:51:05 +0400

The best way to get it fixed is to file a bug and attach a test case.
Cases where "unresolves" are many usually caused by unresolved includes. Can you please try right-click on the project then "Code Assistance->Failed Include...". What do you see there? For example sometimes on Ubuntu I saw similar thing then my GNU compilers got updated and all the cached include paths (they have version number in them) got wrong. If it is the case then resetting toochains in Tools->Options and then Code Assistance->Reparse Project will help the case.

On 07/27/2012 08:00 AM, zachsaw wrote:
There are plenty of bogus red squiggly underlines caused by the parser either 
not in-sync with code or simply because the parser doesn't parse the code 
correctly (it doesn't even parse STL correctly yet at this very early stage).







Red Mark of Death or 'Unable to resolve identifier'

aschwarz1309 07/19/2012

Re: Red Mark of Death or 'Unable to resolve identifier'

Leonid Lenyashin 07/20/2012

Red Mark of Death or 'Unable to resolve identifier'

zachsaw 07/27/2012

Re: Red Mark of Death or 'Unable to resolve identifier'

Leonid Lenyashin 07/27/2012

Red Mark of Death or 'Unable to resolve identifier'

zachsaw 07/30/2012

Re: Red Mark of Death or 'Unable to resolve identifier'

Leonid Lenyashin 07/30/2012

Red Mark of Death or 'Unable to resolve identifier'

zachsaw 07/31/2012

Re: Red Mark of Death or 'Unable to resolve identifier'

Leonid Lenyashin 07/31/2012

Project Features

About this Project

CND was started in November 2009, is owned by Leonid Lenyashin, and has 130 members.
By use of this website, you agree to the NetBeans Policies and Terms of Use (revision 20140418.2d69abc). © 2013, Oracle Corporation and/or its affiliates. Sponsored by Oracle logo
 
 
Close
loading
Please Confirm
Close