>>> David Engster <deng@...> seems to think that:
>I noticed that semantic fails to correctly parse system includes,
>e.g. lines like
>get a red background after a while. Looking at 'cmath', I saw that it
>which is in /usr/include/c++/4.3/i486-linux-gnu. So I added the
>following to my .emacs:
>(semantic-add-system-include "/usr/include/c++/4.3" 'c++-mode)
>(semantic-add-system-include "/usr/include/c++/4.3/i486-linux-gnu" 'c++-mode)
>Now, when I load any c++ file, the variable
>semantic-dependency-system-include-path is correctly showing those two
>paths. But when I fire up the idle work function, e.g. by calling
>semantic-debug-idle-work-function, the variable gets reset to
>after the idle work function has finished. What makes this even more
>strange is that the latter path doesn't even exist on my system.
[ ... ]
Semantic will query your version of gcc by calling "gcc -v" and
parsing the output. I would assume it would show the above version
number 4.2.3. Perhaps you compile with something not called "gcc"?
As I look in semantic-gcc.el, I see there is no configuration variable
for the path to gcc to change. If you aren't using the default gcc,
we should add something so you can update what is being run yourself.
I'm not sure why your explicit configuration is being changed then
restored. Do some of your headers start in c-mode instead of
c++-mode? You may need to add your new headers to both modes?
I'm not sure how to debug a situation where a variable is being set to
some value in an unknown location.
Eric Ludlam: eric@...
Siege: http://www.siege-engine.com Emacs: http://cedet.sourceforge.net