mathiasdm / cdt Goto Github PK

org.eclipse.cdt.internal.ui.text.c.hover

When using implement method,
void blah(const char* arg, ...);
gets as an implementation
void blah(const char* arg) {
}

Make a quickfix 'implement inherited pure virtual methods'.

See the suggestion for an Eclipse checker for unreachable code: https://bugs.eclipse.org/bugs/show_bug.cgi?id=310285

Some include statements, such as <stdio.h> cannot be resolved.
Build up knowledge of the AST and the indexer to find out how to resolve these statements.

A more advanced ControlFlowGraphBuilder could detect more dead code.

Example:

int i = 5;
if(i < 3) {
//doSomething <-- this is dead code
}

Suppose a macro with a few arguments:
BLABLA(argument)

If a user enters: BLABLA(x | y)
If the argument is not surrounded by brackets in the macro expansion, a warning should be shown.

Initialisation of variables in a switch can lead to compilation errors. See https://bugs.eclipse.org/bugs/show_bug.cgi?id=363663

C and C++ make it very easy to add new header includes, but also to build up a huge include structure.
Including a single header can in fact result in hundreds of headers being added to the source code (even though only a few headers are used).

A first issue is transitive header includes.
You include header A, header A includes header B, and in fact, you only need header B. This is a so-called 'transitive header include'. It could be fixed by removing the include of A and adding an include of B.

A second issue is useless header includes. Often headers are added at some point during the project. As the source code changes, these headers might not be needed anymore.