-
Notifications
You must be signed in to change notification settings - Fork 158
New issue
Have a question about this project? # for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “#”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? # to your account
Defining expect(...) macro as shorthand by default conflicts with C++ #143
Comments
We switched it round because when Expecta becomes a framework, the I'm open to ideas around how this could work though. |
IIRC, the reason |
e.g.: /// Someheader.h
static inline __attribute__((overloadable)) expect(NSInteger i) {
EXP_expect(@(i)); // or whatever
} |
There's also the matter of populating the |
Ah, dang. |
@itsthejb Could you post the exact compilation error you're seeing? To reproduce, is it enough to simply import |
Of course, if ComponentKit is imported first you can dodge this problem, but the doesn't really solve the problem that as a macro it has a lot of scope to stomp on things... |
Any updates on this? |
Hi all,
We have started mixing C++ into our projects now that we're using ComponentKit. Needless to say this brings up a few interoperability issues. In the case of Expecta, I noticed that defining the
expect(...)
macro as shorthand by default provides no way to avoid name conflicts with libstdc++ (in this case<iterator>
). Whilst it's possible to just not import Expecta for these specs, this might be a nice-to-have worth addressing in a future release.Thanks!
The text was updated successfully, but these errors were encountered: