#19 request for scoping functionality

[Anonymous]

would be useful if we have scoping functionality. This
can be implemented as a second layer filtering.
Example:

struct foo {
int x;
}

struct bar {
int x;
}

when scope is set to foo, then display the result of foo's
x, and filter out bar's x.

even more, extend the scoping functionality to scope file
name as well.

In a large project, and multi platform for example:

def_intel.c:
struct foo {
int x;
}

def_powerpc.c:
struct foo {
int x;
}

if filescope is set to intel, and search for x, the result
should only display foo's x in def_intel.c

[Hans-Bernhard Broeker]

Logged In: YES
user_id=27517

Sorry, but while this might sure be nice to have, it almost
certainly can't be done, short of rewriting cscope from scratch.

It might be possible to implement this for "find
definition", but there's no way this can work for "find
symbol" using a tool even remotely resembling current
cscope. Our C parser doesn't even try to record as much
information as it would take to resolve this. It'd have to
become essentially all of a complete C compiler and linker
(and need a lot of information usually not recorded in
source files at all, but only in platform-specific ways,
like makefiles or IDE project definitions) before it could
have any chance to know which variable is of which type,
defined in which file. This is *way* beyond the scope of a
source code navigation tool.