[Mono-list] Re: Mono CVS: mcs gvaish

[Rhys Weatherley]

Miguel de Icaza wrote:

> So the `Mono.' namespace rule should just apply to classes that for some
> reason we have to expose to the world, but are not part of the standard
> (for example, we might need a gateway to communicate say the System
> assembly with our corlib implementation).

Could you choose a name other than "Mono" for these
classes?  There are other projects that may be interested
in using pieces of your library, and it will be strange
(to say the least) to have "Mono" scattered throughout
their code.  It will get even stranger if, for some reason,
you decide to rename the project in the future.

I personally prefer completely neutral names that still
remain relevant when the environment changes.  I suggest
the "OpenSystem" name that someone proprosed recently.
Or perhaps just "Private" if the classes are intended
solely for interfacing between assemblies.

The same comment also applies to the choice of class
names within the namespace.  i.e. "PrivateFoo", not
"MonoFoo".

Cheers,

Rhys.