in my opinion the naming conventions you chose for Obj-B collide with Cocoa's conventions. Cocoa uses lowercase camel notation, so that messages (e.g. + (id)data ) and attributes start with a lowercase character. Obj-B on the other hand uses uppercase camel notation (e.g. Contains for arrays). The collision occurs as soon as I start declaring plain Cocoa messages to be used as functions or subs within my code. I can extend the functions of the built-in Obj-B array class by declaring the messages provided by NSMutabeArray. But now I have lowercase and uppercase camel notation for the same concept.
I don't know how big the overhaul would be to switch Obj-B to lowercase camel notation as well.
MacBook (2GHz, 4 GByte) - Lion (10.7.3)
started Objective Basic coding in April 2010 - still enjoy it