3 ms·
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
by LeoNatan25 13y ago
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?
- kennywinker 13y agoIf 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.
- gress 13y agoApple is incorporating his open source project. Whatever names he uses, they will use when they pull the latest version.
- paxswill 13y agoThe name wouldn't be static. To try to make it more obvious: [CLASSNAME insertCLASSNAMEInManagedObjectContext:moc]
- twic 13y agoSorry 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.