-
Notifications
You must be signed in to change notification settings - Fork 59
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
Support for C++ #26
Comments
@FramusRock good idea thanks, are you using .cpp and/or .mm files for c++? btw, you're welcome to submit a pull request if you want to implement it. |
In .mm files #import works just fine. I'm talking about .cpp in which #include is a must. Auto-Importer works just fine there, it should just write #include instead of #import ;) |
I looked into it a little, maybe you can help me out, so that I can make an appropriate pull request. In LAFIDESourceCodeEditor.m, there is this:
How can I find out if the current file that this header belongs to is a CPP file or ending in .cpp? |
I'm still interested in it, could you give me a hint how I can achieve it, please? |
hey @FramusRock I spent some time trying to figure out how to get the filename from current editor but still no luck. Another approach would be to get the first existing import/include line on the file and use that to decide if you should be using #import or #include |
hey @lucholaf , thank you. I also spent some time on it, but also didn't have any luck getting it right. |
@FramusRock +1 |
I made it! Pull request sent! |
Hey,
I absolutely love your tool and use it everyday!
Is it somehow possible (maybe with a setting or auto-recognize) to use #include instead of #import when coding C++ in Xcode?
The text was updated successfully, but these errors were encountered: