[jsr294-modularity-eg] Problems for JSR 294 to address

[Michal Cierniak]

I agree with the general point you're both making but I don't think
that namespaces in .NET are any more hierarchical than packages in
Java.  Can you guys provide some reference for the existence of
hierarchical namespaces in .NET?  My understanding (perhaps incorrect)
is that while it is true that C# (the language) has the "namespace"
keyword, the .NET framework doesn't have this notion at all.  This is
definitely what the CLI spec says (in the very beginning of Partition
II, Standard 6):

"While some programming languages introduce the concept of a
namespace, there is no support in the CLI for this concept. Type names
are always specified by their full name relative to the assembly in
which they are defined."

On Tue, Jan 27, 2009 at 2:00 PM, Daniel Leuck <dan at ikayzo.com> wrote:
>> Interestingly, in my
>> understanding, .NET makes such a distinction between the modularity of a
>> delivery unit (called an assembly) and the finer grained modularity inside a
>> delivery unit, represented by namespaces. The "internal" keyword indicates
>> that the artifact is visible only inside an assembly and the "namespace"
>> keyword provides a hierarchical namespace.
>
> That is correct, and I think the "internal" visibility specifier in C#
> makes more sense than what we currently have in java. I think
> visibility within a module is probably the most commonly required
> level after public and private.
>
> Dan
> _______________________________________________
> jsr294-modularity-eg mailing list
> jsr294-modularity-eg at cs.oswego.edu
> http://cs.oswego.edu/mailman/listinfo/jsr294-modularity-eg
>
_______________________________________________
jsr294-modularity-eg mailing list
jsr294-modularity-eg at cs.oswego.edu
http://cs.oswego.edu/mailman/listinfo/jsr294-modularity-eg