-
Notifications
You must be signed in to change notification settings - Fork 255
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
In xcode 6 beta4 building shows a couple of warnings #67
Comments
I noticed this too in Xcode 6 and I've fixed it in my fork and created a pull request. |
Hopefully it gets merged in! |
I hope so too, but the warnings are pretty harmless but nonetheless annoying. |
Yeh, please merge this. Quite an aggressive warning by X-Code though. |
Not a big issue.. but I would love to see it fixed! |
Bumb. I believe in zero-warnings code policy. |
I'm just looking this problem over again. The issue is that - (instancetype)initWithObjects:(const id [])objects forKeys:(const id [])keys count:(NSUInteger)cnt is the designated initializer in the superclass and this subclass overrides this method and calls an overridden convenience initializer from this overridden designated initializer. So, we've switched the designated initializer from that found in the superclass to the subclass. I'm not entirely sure how to solve this, but one workaround is to override this method with an NSAssert to prevent it from being called directly from CHCSVParser. You could just comment out this overridden designated initializer but then I suppose it's possible that somebody could call this method from CHCSVParser and generate an unexpected result. Please let me know your thoughts, if that seems like a reasonable approach I'll do a pull request with the solution. |
I am no longer seeing warnings in Xcode 6, so I guess this issue can be closed @davedelong. |
I'm still seeing it in the release version of Xcode 6. |
You are right; my dependency manager still used my own fixed branch. It seems @davedelong has implemented a fix, however CocoaPods.spec is still set to the tag 2.1.0 of July 2014 so any commits after that are not included. If @davedelong would release a new tag, the warnings would disappear. |
As a workaround you could temporarily use this in your Podfile: This just uses the master branch instead of tags |
Ok, cool. @edwardmp thanx for the info. |
The text was updated successfully, but these errors were encountered: