tag:blogger.com,1999:blog-6864853053396532264.post4151444432957538588..comments2024-01-25T06:36:43.336-07:00Comments on Osmorphis: Private Methods in Objective-CJEShttp://www.blogger.com/profile/05678402081101110580noreply@blogger.comBlogger2125tag:blogger.com,1999:blog-6864853053396532264.post-88594215181083083662009-02-19T10:00:00.000-07:002009-02-19T10:00:00.000-07:00Yes, with added hassle. One question I have concer...Yes, with added hassle. One question I have concerning this technique is: can implementation code for the same class in another file access private methods declared and defined in a different file? My guess is no, so do we need a private .h file to declare all the privates? <BR/><BR/>The hassle factor for private methods is really starting to pile up. I always question private methods in the first place.JEShttps://www.blogger.com/profile/05678402081101110580noreply@blogger.comtag:blogger.com,1999:blog-6864853053396532264.post-56337204528200202352009-02-18T17:35:00.000-07:002009-02-18T17:35:00.000-07:00It is good that you don't have to prototype privat...It is good that you don't have to prototype private methods in the header file. You can still call private methods publicly with only a warning. If you switch the order of the private methods, you'll get a warning. A common practice is to create a Category in the implementation file to forward prototype all private methods.Anonymousnoreply@blogger.com