Proposed improvements to the separate compilation model

[bearophile]

Andrei:

> I don't think it's an either-or situation.

OK, but first it's better to work as much as possible on the automatic/compiler side of things, and see how much far it goes. Turning .di files into hand-written things has to be left as very last chance.


> For a variety of reasons, 
> some organizations want separate control of the "declaration" and 
> "definition" files.

Example: to not give full source code to clients. Even Python (that today is far more used in large and medium organizations than D) has received similar pressures. But each of those pressures have disadvantages, sometimes for the community of the programmers. So Python has chosen to resist to some of those pressures.


> Inability to do so is a common criticism leveled 
> against Java and one of the reasons for the proliferation of XML 
> configuration files and dynamic loading in that language.

There is JSON too today :-) Dynamic loading is a source of many troubles, it seems hard to make it safe.

Bye,
bearophile