On May 10, 2011, at 8:26 PM, William Squires wrote: > 5) Along with #1 above, a way to encrypt/decrypt the .m part so that the > whole shebang could be sold to other developers without exposing the > 'how-does-it-work' underneath (unless they pay extra for the right to view > the source!) There would be two encryption keys; one to unlock a 'read-only' > mode, and another to unlock full 'read/write' capability. The .h part would > be visible in any case; it wouldn't be encrypted. This exists. Compile your code into a framework. Make private methods private. Include headers and documentation.
_______________________________________________ Cocoa-dev mailing list (Cocoa-dev@lists.apple.com) Please do not post admin requests or moderator comments to the list. Contact the moderators at cocoa-dev-admins(at)lists.apple.com Help/Unsubscribe/Update your Subscription: http://lists.apple.com/mailman/options/cocoa-dev/archive%40mail-archive.com This email sent to arch...@mail-archive.com
