Surpress "multiple methods named" error

[soffes]

I realize that collection won't always be an NSArray, but the cast will let the compiler know to expect a NSUInteger return type instead of size_t which is also a return type a method named count inside of JSONKit.

[johnezang]

Well, actually, collection will never be a NSArray.. :) It will always be a JKDictionary or a subclass, but the documentation specifically states that JKDictionary is a private, internal class that must not be subclassed, so...

Technically, this is the count method that's being called, since JKDictionary is (obviously) a concrete class of the NSDictionary class cluster. The cast you added is part of the NSEnumerator object, which is needed to implement the required class cluster primitive method keyEnumerator (see also Methods to Override).

I don't mind the pull request, but you should change it to (NSDictionary *). :) Also, can you post the specific warning you were getting? I did a quick check with grep, both of JSONKit and Foundation/Headers/*, and I didn't see an obvious conflict, but there was a lot of cruft to sort through.

[soffes]

Here's the error:

/Users/samsoffes/Code/synthetic/REDACTED_APP/Vendor/JSONKit/JSONKit.m:851:22:{851:22-851:40}: error: multiple methods named 'count' found [-Werror,3]
   NSUInteger count = [collection count], atObject = 0UL;
                      ^~~~~~~~~~~~~~~~~~
/Developer/Platforms/iPhoneOS.platform/Developer/SDKs/iPhoneOS5.0.sdk/System/Library/Frameworks/Foundation.framework/Headers/NSArray.h:16:1:{16:1-16:21}: note: using
 - (NSUInteger)count;
 ^~~~~~~~~~~~~~~~~~~~
/Users/samsoffes/Code/synthetic/REDACTED_APP/Vendor/HipstaProcessor/HipstaProcessor/HPKernel.h:19:49:{19:49-19:54}: note: also found
 @property (nonatomic, assign, readonly) int16_t count;
                                                 ^~~~~
/Developer/Platforms/iPhoneOS.platform/Developer/SDKs/iPhoneOS5.0.sdk/System/Library/Frameworks/CoreImage.framework/Headers/CIVector.h:61:1:{61:1-61:17}: note: also found
 - (size_t)count;
 ^~~~~~~~~~~~~~~~
1 error generated.

[johnezang]

Ah, well, that explains why I didn't find it, and why it never tickled a compiler warning for me. I usually make an effort to crank up the compiler warnings to crazy levels before committing something to the repo, but you can't catch them all. For practical reasons, I only test against the "common" frameworks, and CoreImage doesn't make the cut. :)

[soffes]

Haha definitely. Thanks for merging :)