On 07/08/2010 22:05, Walter Bright wrote:
Don wrote:
Seems pretty clear that the problems are with the concept itself,
rather than D's implementation of it.
That leads me to be cautious in rushing in to 'fix' it.
Yeah, there is some relevant things I want to say on this issue of
component encapsulation, especially coming from the Java world. I think
they are really relevant insights from there.
In summary, I think the ideal would be to have something like OSGi has:
a bundle system. That's a really good way to have component
encapsulation and version/dependency management scale to really large
apps, built from several separate, and well "encapsulated", components.
The alternative "@internal" proposal is somewhat limited, it would only
be a very minor improvement. (a related concept exists in OSGi bundles
though) Also, I think this can be dealt with without involving the
compiler (although a standard will be very important).
I'll try to make a more detailed exposé, when I have more time, so that
the use case be better understood. I'll post it on the bug report itself:
http://d.puremagic.com/issues/show_bug.cgi?id=2529
--
Bruno Medeiros - Software Engineer