[Mono-list] namespace problem

[Sean MacIsaac]

Hello,

There is no need to declare them in a different namespace.  You can just
use System.  The compiler will give you a warning.(1595) which is a
redefinition warning, but it uses the one explicitly defined in the code
rather than the one in Microsoft's libraries.  In this way if you have
System.Collections.* implemented, and that references Array, there is no
problem as the Microsoft version of Array will be used with your
System.Collections.*.

I spent all of yesteday getting rid of compiler errors that were present
in the code in Ximian's CVS (which to the best of my knowledge will be
put up publicly by Miguel in the next few days, hopefully today).

You can disable the warning with a /nowarn:1595 on the csc command line,
which is what I've done in our command line.  Hopefully this weekend I
will also fix up the maintainer/progress script so that it accurately
reflects what is in our library now, and have it push to the website on
a regular basis.

Sean

On 14 Jul 2001 03:39:03 -0700, Sebastien Lambla wrote:
> Hello all,
> 
> while implementing classes, it occured to me there was a namespace
> problem... For development and testing purpose, I'm putting all the classes
> under the Mono.System namespace. When calling a class in this namespace from
> another class in this namespace too, the compiler seems not to want to link
> anything from the mscorlib System namespace...
> 
> For ex:
> namespace Mono.System
> 	{
> 	class Type
> 		{
> 		// whatever
> 		}
> 	class access
> 		{
> 		// Here, what code should be used for the System.Type and not the
> Mono.System.Type? Using System.Type just goes back to Mono.System.Type
> (because of the namespace declaration...)
> 		}
> 
> 	}
> 
> Sebastien Lambla
> 
> 
> _______________________________________________
> Mono-list maillist  -  Mono-list@ximian.com
> http://lists.ximian.com/mailman/listinfo/mono-list