Semantic Anomaly

I cannot really post any code example because of Copyright but I have
something like this:

void someFunc ( SomeClass&                 refToSomeClass,
                const NS1::SomeOtherClass& refToSomeOtherClass )
{
  refToSomeClass. // does not work
  refToSomeOtherClass. // does work
}

The odd thing is when you put the cursor over a type the minibuffer
generally brings up:

SomeOtherClass.h: class SomeOtherClass

And, this is very much the case for SomeOtherClass, however, when I put the
cursor over SomeClass I get:

SomeClass.cpp: void ~SomeClass (void)

So, in the example which does not work: SomeClass, semantic is bringing up
the destructor and why I cannot figure out.

I can offer a more comprehensive example but it will take me a while to
emulate what is going on. I ask here because perhaps one of the developers
have come across such an issue.

Cheers.


------------------------------------------------------------------------------
Dive into the World of Parallel Programming! The Go Parallel Website,
sponsored by Intel and developed in partnership with Slashdot Media, is your
hub for all things parallel software development, from weekly thought
leadership blogs to news, videos, case studies, tutorials and more. Take a
look and join the conversation now. http://goparallel.sourceforge.net