News for hackers. Stuff that matters.
Re:Objective Next by necubi on Friday March 21, 2014 @06:10PM (#7445271)
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.
Re:Objective Next by K0nserv on Friday March 21, 2014 @06:31PM (#7445371)
I 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
Re:Objective Next by frou_dh on Friday March 21, 2014 @06:18PM (#7445304)
Stockholm syndrome from too many years in the company of archaic compilation models: it's real and it's scary!
Re:Objective Next by pjmlp on Saturday March 22, 2014 @02:47AM (#7448071)
It 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.
Re:Objective Next by i386 on Friday March 21, 2014 @07:01PM (#7445527)
Only worth doing if there are some directives added for public/private directives.

Exposing internals is still bad design.