News for hackers. Stuff that matters.
Re:Apple Claims Mogenerator's Methods by twic on Saturday April 12, 2014 @05:15PM (#7579236)
How about putting some distinctive string in the generated method name? Like:

  [MyEntity insertMyEntityInManagedObjectContext:moc];
Yes, it's redundant and crappy. But it's not a disaster and it should avoid the great stamping boot of Apple.
Re:Apple Claims Mogenerator's Methods by LeoNatan25 on Saturday April 12, 2014 @08:09PM (#7579654)
When Apple upgrades their code, they'll have the same "distinctive string" and the cycle continues. Or do you suggest people go in potentially tens or hundreds of classes and change manually the methods and their use?
Re:Apple Claims Mogenerator's Methods by kennywinker on Saturday April 12, 2014 @08:36PM (#7579716)
If the entity name is part of the method name, it'll be different so long as you don't overlap entity names with Apple.

It'd be a lot of work for devs to change code that calls those methods, but not so much it's not a possible solution. I'm optimistic someone inside Apple will address this issue on their end, but if that fails this sounds like a possible workable solution.

Re:Apple Claims Mogenerator's Methods by gress on Saturday April 12, 2014 @11:58PM (#7580163)
Apple is incorporating his open source project. Whatever names he uses, they will use when they pull the latest version.
Re:Apple Claims Mogenerator's Methods by paxswill on Sunday April 13, 2014 @04:34PM (#7582885)
The name wouldn't be static. To try to make it more obvious:

    [CLASSNAME insertCLASSNAMEInManagedObjectContext:moc]
Re:Apple Claims Mogenerator's Methods by twic on Sunday April 13, 2014 @05:58PM (#7583257)
Sorry i didn't make this clearer. I was suggesting that the class name could be used in the method name. As long as nobody names their classes the same as Apple, their method names will also be different.