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

Rhys Weatherley rweather@zip.com.au
Sat, 01 Dec 2001 14:10:49 +1000

Miguel de Icaza wrote:

> > 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.
> It really does not matter that the name is Mono, that is the point of an
> internal class.

It does matter to me.  I don't believe you are giving enough
thought to making the code generic across implementations.

Naming things based on your own implementation enforces
a mode of thinking where no other project matters.  This will
quickly lead to "Oh, just make a PInvoke call to monoblah.so
to get the implementation".  This isn't reusable.

Since Portable.NET is the "designated other project", this
bugs me.  I'd like to reuse some of the upper-level Mono
libraries, but not if I have to rewrite them to remove

It's not a technical thing.  It's a mindset thing.  I only ask
that you think about the needs of other projects, especially
in the upper layers.