-
Notifications
You must be signed in to change notification settings - Fork 1.6k
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
RFE: Switch Header/Source command support for files with *.cc extension. #1341
Comments
What is the extension of the header file? "*.cc" is supposed to work. We need more repro details. Does this repro for certain file names or for certain directory structures? What does the bottom right database icon say? Our system needs to have located the target file on disk and added it to our database before it can go to it. Also, if there's a red flame in the bottom right, the IntelliSense thread could be blocking the switching header. |
I've zipped up a setup that reproduces the problem for me. As it is, if you open the folder and open Hope this helps. |
@photex Thanks a lot for the repro -- I'm hitting the problem now. This is strange. I'll investigate... |
Oh, it's because the header file has the hpp extension and the system is setup to only switch cc files to .hh or .h files. This decision was made before I joined so I'm not sure what the reasoning was. Is there a reason your source is .cc and your header is .hpp? It seems inconsistent. |
We've changed it to switch from to any of .h/.hpp/.hxx/.hh from any of .c/.cpp/.cc/.cxx (not sure yet when the fix will be released). We eventually want to fix it to work on any extensions (I think another issue is tracking that). |
Awesome! Glad I could help. I don't know why they were named that way. I think .h was reserved for C interfaces and the header had to be something different. .hpp seems to be the vernacular for c++ interfaces. .cc was kinda left field. :D |
Fixed with 0.14.5. |
Howdy!
I recently opened a project that used *.cc for c++ files and the Switch Header/Source command had no effect. Upon renaming one of the source files the command worked as expected.
Cheers!
The text was updated successfully, but these errors were encountered: