|
|
|
|
|
|
by pjmlp
411 days ago
|
|
|
Java modules have nothing to do with that, rather not all packages are supposed to be public rather sub-packages as way to have clean implementations, but given the granularity, many developers end up relying on internals that were designed only for consumption from public APIs. .NET Assemblies suffer from the same, unless you make use of some tricks like InternalsVisibleTo attribute. During the .NET 1.0 days there was the idea to have components, for a role similar to how Java modules have come to fulfill, but it never took off, and the idea was confusing as many developers usually thought they related to COM, when they heard "components" alongside .NET. https://learn.microsoft.com/en-us/dotnet/framework/app-domai... |
|
|