java.lang.NullPointerException
at
org.eclipse.cdt.internal.ui.workingsets.IWorkingSetProjectConfigurationFactory$Registry$1.compare(IWorkingSetProjectConfigurationFactory.java:180)
at
org.eclipse.cdt.internal.ui.workingsets.IWorkingSetProjectConfigurationFactory$Registry$1.compare(IWorkingSetProjectConfigurationFactory.java:1)
at java.util.TimSort.countRunAndMakeAscending(TimSort.java:352)
at java.util.TimSort.sort(TimSort.java:216)
at java.util.Arrays.sort(Arrays.java:1438)
Change-Id: Ibe91a679c876ed5f70f4f787188e13e52203466c
Signed-off-by: Alena Laskavaia <elaskavaia.cdt@gmail.com>
- Test case for reproducing the problem.
- The code is lost because a copy of the body, which contains macro
references is not rewritten, but its raw signature is taken. The raw
signature of a copy is empty in this case. I've solved this issue by
using the raw signature of the original node for get raw signature. This
is a fundamental change of ASTNode.getRawSignature(). We could also
solve this in the StatementWriter to get the original node before
accessing the raw signature.
Change-Id: I64b408b09444df818d30d99d99de4a1974eacf93
Signed-off-by: Thomas Corbat <tcorbat@hsr.ch>
Reviewed-on: https://git.eclipse.org/r/39406
Tested-by: Hudson CI
Reviewed-by: Sergey Prigogin <eclipse.sprigogin@gmail.com>
Add a hidden preference "org.eclipse.cdt.core/validate_include_entries"
which allows to disable validation of include entries if set to false in
plugin_customization.ini.
Change-Id: Ia80f875228a459589ab8a4e6733d3e2f723f78d3
Signed-off-by: Anton Leherbauer <anton.leherbauer@windriver.com>
Reviewed-on: https://git.eclipse.org/r/39642
Tested-by: Hudson CI
class templates of a class template
There are 2 changes. Finding the proper naming scope, which basically is
the same as what is done in CPPUnknownTypeScope.getBindings when
retrieving the bindings themselves.
The second change was picking the right scope for the actual
accessibility check for base templates.
Change-Id: I535c8cdd9d07272d37da9d23a03edb9e6b1b3a7a
Signed-off-by: Michi <woskimi@yahoo.de>
Reviewed-on: https://git.eclipse.org/r/39016
Reviewed-by: Sergey Prigogin <eclipse.sprigogin@gmail.com>
Tested-by: Sergey Prigogin <eclipse.sprigogin@gmail.com>
class
The problem was with template base classes as in the unit test.
Accessibility check did not find the proper AccessContext.namingClass
and always ended further up in the class tree.
Change-Id: I447567cabd20ad5c57c05a9ffa5f0f12c5321ccf
Signed-off-by: Michi <woskimi@yahoo.de>
Reviewed-on: https://git.eclipse.org/r/38944
Tested-by: Hudson CI
Reviewed-by: Sergey Prigogin <eclipse.sprigogin@gmail.com>
Tested-by: Sergey Prigogin <eclipse.sprigogin@gmail.com>
When the nodeSelector detects an IASTNode that has a TemplateId parent
we use that instead of the original. The benefit is that we also get the
template parameters so we can find template specialization matches.
Change-Id: I3751efdb15e868b4aa6688ad338227e0d0c5bcd8
Signed-off-by: Michi <woskimi@yahoo.de>
Reviewed-on: https://git.eclipse.org/r/38923
Tested-by: Hudson CI
Reviewed-by: Sergey Prigogin <eclipse.sprigogin@gmail.com>
Tested-by: Sergey Prigogin <eclipse.sprigogin@gmail.com>
class
This should work now for AliasTemplates from AST and PDOM.
SourceHover is also affected.
Are there any unit tests for this?
Change-Id: I54a9c2d6cd0851f901b917a57d79616298699299
Signed-off-by: Michi <woskimi@yahoo.de>
Reviewed-on: https://git.eclipse.org/r/38919
Tested-by: Hudson CI
Reviewed-by: Sergey Prigogin <eclipse.sprigogin@gmail.com>
Tested-by: Sergey Prigogin <eclipse.sprigogin@gmail.com>
