News for hackers. Stuff that matters.
Re:Apple's Module proposal to replace headers for C-based la... by Nursie on Tuesday November 27, 2012 @05:16AM (#4836499)
Anyone saying 'inherently unscalable' about a feature of a language that's used in as many places as C needs to really think about things...

I understand some of the objections, and the import mechanism doesn't sound like a bad thing, though some of the objections are weird -

Import only imports the public API and everything else can be hidden - who wasn't doing this for libraries or large code modules anyway? Have static functions at the code module level, 'private' headers for sharing functions within a larger logical module and public headers at the logical module or libary level. Is this too cumbersome?

Re:Apple's Module proposal to replace headers for C-based la... by pmr_ on Tuesday November 27, 2012 @07:06AM (#4836774)
The problem with implementation hiding is that it is impossible to do well with templates. You will always make all implementation details available to your a user of your header and sometimes the implementation details are a public API themselves (libc++ vector brings in almost all of utility, a bunch of type_traits and so on).