News for hackers. Stuff that matters.
Re:Objective Next by bwindels on Friday March 21, 2014 @06:08PM (#7445265)
How is it worse?
Re:Objective Next by K0nserv on Friday March 21, 2014 @06:27PM (#7445350)
Separation of interfaces and implementation is a core component of pre compiled code distribution, .h files + compiled library.

By simply glancing over a header file one can achieve a quick idea of the interface without consulting the documentation. It's self documenting, reading a Java file in the same way is impossible.

Forward declaration in header files and imports in implementation is also a huge benefit in compilation speed and complexity.

Re:Objective Next by frou_dh on Friday March 21, 2014 @06:37PM (#7445412)
The point is that writing and maintaining such files by hand is a tremendous waste of time.

When I last used C#, I remember Visual Studio would extract and display such public overviews directly from compiled .NET assemblies.

Even if no IDE is involved, something could just auto-generate a text file for distribution. It could even be adorned with a .h file extension for faux-retro appearance!

Re:Objective Next by K0nserv on Friday March 21, 2014 @06:48PM (#7445463)
I do agree partially about the repetition issue, but with a language such as Objective-C you'll auto complete every definition the second time which hardly takes a second, especially with fuzzy auto completion. If time saving is the goal the naming convention for methods is a far better candidate for change
Re:Objective Next by frou_dh on Friday March 21, 2014 @06:56PM (#7445500)
Zapping the entirety of an unnecessarily manual practice is going to be objectively better than providing some typing assistance for it.
Re:Objective Next by K0nserv on Friday March 21, 2014 @07:18PM (#7445609)
There are still use cases for header files which would require additional syntax if headers are to be generated from .m files. Also the use case of forward declaration comes to mind which would totally lost with an implementation only system
Re:Objective Next by to3m on Friday March 21, 2014 @09:00PM (#7446329)
You wouldn't need any of this if it were done properly. C# is a good demonstration of the principle and I'm sure Java could support something similar. In the case of C#, forward declarations are unnecessary, and if you want/need to see something like a .h file then one can be generated automatically from the metadata included in the binary.

In fact Objective-C already includes pretty much everything necessary in the binary already, as you can see by using class-dump. Perhaps additional work would be required to support exposing absolutely everything that might be required, but there's no obvious reason why the language couldn't be extended to allow direct use of compiled code, with no need for a .h file.

Re:Objective Next by frou_dh on Friday March 21, 2014 @07:31PM (#7445682)
There is no .m .h .c .cpp involved. In hypothetical new language we cast off all baggage and stop thinking in archaic C and "C with a twist" terms.
Re:Objective Next by pjmlp on Saturday March 22, 2014 @02:43AM (#7448065)
- Turbo Pascal

- Object Pascal

- Delphi

- Modula-2

- Modula-3

- Oberon

- Active Oberon

- Component Pascal

- OCaml

- Haskell

- D

- Ada

- Eiffel

- ...

All languages with native code compiler available, where the header files can bot the manually or automatically generated from the implementation.

Many of them have, or used to have, code browsers and auto complete by reading the metadata stored in the binaries.

C based toolchains are still at stone age, in terms of modular programming support.

Re:Objective Next by rossjudson on Friday March 21, 2014 @07:41PM (#7445720)
That's what javadoc is for. You get a lot more out of browsing through that, than header files.