Compiler warnings on NSManagedObject+MagicalDataImport.m #101

Closed
mmittelman opened this Issue Dec 9, 2011 · 3 comments

Projects

None yet

3 participants

@mmittelman

PerformSelector may cause a leak because its selector is unknown.

It would be great to get rid of these warnings.

@magicalpanda

These warnings should already have been silenced through pragmas. If I missed one, can you please let me know where it's complaining?

@mmittelman

I removed MR from my project since I had so much trouble finding example of implementation. It seemed really great, especially since I'm having issues with CoreData and threads. Please make a real sample project.

@XMLSDK
XMLSDK commented Dec 10, 2011

From NSManagedObject+MagicalDataImport.m it complains about "NSString may not respond to MR_capitalizedFirstCharaterString". It may because there does not exist ```
@interface NSString (MagicalRecord_DataImport)

  • (NSString *) MR_capitalizedFirstCharaterString;
    @end```

Also, Xcode also warns about
if (implementsShouldImport && !(BOOL)[self performSelector:shouldImportSelector withObject:singleRelatedObjectData]) and
if (!(implementsShouldImport && !(BOOL)[self performSelector:shouldImportSelector withObject:relatedObjectData])) that
Cast from pointer to integer of different size. Shouldn't the right way to test id is == nil ?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment