3 ms·
I, and basically every language designer since the 80s has disagreed with this. It's needless repetition: all of the information contained in the .h file is dup
by necubi 13y ago
I, and basically every language designer since the 80s has disagreed with this. It's needless repetition: all of the information contained in the .h file is duplicated in the .m file. If you really want a nice listing of the exported methods, it's easy to generate that from the .m file.
- frou_dh 13y agoStockholm syndrome from too many years in the company of archaic compilation models: it's real and it's scary!
- pjmlp 13y agoIt is incredible how C based compilation models become so widespread, that younger programmers are completely unaware of sane module systems in other languages with ahead of time compilation toolchains.
- K0nserv 13y agoI agree that there is some merit in the repetition argument, but when discussing a language like Objective-C we must consider that any Objective-C programmer is surely using auto completion to the fullest extend due to the extremely verbose nature of Objective-C naming conventions. The point being that the repetition time is negligible
- i386 13y agoOnly worth doing if there are some directives added for public/private directives. Exposing internals is still bad design.