class Foo;
class Foo1
{
...
private
Foo *pUseFoo;
};
class Foo2
{
...
private
Foo *pUseFoo;
};
...
class Foo
{
...
};
I see the forward declaration of the class in the method list! Why? It isn't so useful. When I want to get to class Foo I need to select the second entry of the method list. Mostly I missed it.
This is the same for function declarations...
Solutions: - Use another different symbol - Use an option to filter it - Set a semicolon behind the forward declaration and periods for the definition. (or similar)
Just my 2 cents.
Martin Richter [rMVP] WWJD http://blog.m-ri.de "A well-written program is its own heaven; a poorly written program is its own hell!" The Tao of Programming
I have edited the code slightly, to make sure it compiles, so I have a valid test here. I am not seeing this, the forward declaration is not being shown for me. I have attached screen shots of what I am seeing, along with my Alt-M list options for clarity, using VS2022 and VA 2491.0
The first entry brings me to the forward declaration CDlgJobEditorSheet. The second to the class.
Martin Richter [rMVP] WWJD http://blog.m-ri.de "A well-written program is its own heaven; a poorly written program is its own hell!" The Tao of Programming
I am using VS2022. I try to create a "minimum repro test case".
Martin Richter [rMVP] WWJD http://blog.m-ri.de "A well-written program is its own heaven; a poorly written program is its own hell!" The Tao of Programming
Found the "problem", which is fairly obvious when you know what is going on. Forward declares are NOT shown in the Alt-M list if you are testing in a cpp file, but they ARE shown if you are testing in a header file. It never occurred to me that the file extension would matter, but I ran into this when running some more tests on this.
It turns out this has come up once before, so I have added this vote and information to the case:
Martin Richter [rMVP] WWJD http://blog.m-ri.de "A well-written program is its own heaven; a poorly written program is its own hell!" The Tao of Programming