Re:Why C++ Is Not "Back"
by cousin_it on Sunday December 02, 2012 @08:16AM
(#4861095)
If C++ lets you optimize the readability of callers at the expense of callees, that doesn't mean you can optimize a whole system for readability, because it will contain both callers and callees. In Java it's common to have systems that are pretty uniformly readable.
[ Parent
| on HN ]
Re:Why C++ Is Not "Back"
by fauigerzigerk on Sunday December 02, 2012 @09:47AM
(#4861322)
I agree, C++ encourages a seperation between library writers and library users. That's not good.
In Java, however, lots of things are done outside of the language to solve similar meta-programming issues. For instance, many of the new annotations are only available within a suitable container that interprets them at runtime. Some of these things even need byte code manipulation. The resulting system is not generally simpler than C++ in my opinion and you have the same separation between library/container/runtime makers and mere users.