News for hackers. Stuff that matters.
Re:Apple's Module proposal to replace headers for C-based la... by shadowmint on Monday November 26, 2012 @07:05PM (#4834741)
Sounds interesting, but I've got to admit my initial response is cautious.

How will this avoid the LD_LIBRARY_PATH hell of trying to depend on a local module (ie. conflicts)?

How will it work at all with local submodules inside a single project? (ie. I have 200 local c files, each with a header. Now what? A module each? How do we handle simple dependencies between classes and functions?)

How will we import actual macros?

My guess is that the answers are:

1) include path style --module-path=blah

Seems fair, but this is going to be as messy as include paths already are.

2, 3) dont use modules except at a system level.

Thats a shame as far as im concerned, but perhaps I'm wrong. Can anyone else see how these might work?

There are no comments on this comment yet.