New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Headers with "_p.h" suffix do not get resolved in Xcode for automatic-tracking of counterparts #93

Closed
kevinleeMW opened this Issue Apr 15, 2016 · 1 comment

Comments

Projects
None yet
2 participants
@kevinleeMW
Contributor

kevinleeMW commented Apr 15, 2016

Private headers with "_p.h" suffix do not get resolved in Xcode for automatic-tracking of counterparts.

Xcode has a feature that automatically detects source files' counterpart header file and displays it in the assistant editor, as long as the source and header files have the same file name excluding the extension.

Because some source files have their counterpart headers with "_p.h" suffix, Xcode is not able to detect the counterpart headers automatically.

@saschazelzer

This comment has been minimized.

Show comment
Hide comment
@saschazelzer

saschazelzer Aug 12, 2016

Member

There are no _p.h headers any more, so I am closing this.

We still have header files where the definitions for symbols live in a differently named .cpp file (e.g. a Some.h and a SomePrivate.h header where all definitions are contained in a common Some.cpp file). If this is still an issue, we can consider splitting the .cpp file.

Member

saschazelzer commented Aug 12, 2016

There are no _p.h headers any more, so I am closing this.

We still have header files where the definitions for symbols live in a differently named .cpp file (e.g. a Some.h and a SomePrivate.h header where all definitions are contained in a common Some.cpp file). If this is still an issue, we can consider splitting the .cpp file.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment