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

[A Rafael D Teixeira]

First, just one of my comments:
I donīt know why Rhys has objections to Mono root namespace. Would he ask 
Microsoft not to use the Microsoft root namespace? Would he prefer to have a 
Ximian namespace (a company-based namespace instead of project-based 
namespace)?

Namespaces exist just to avoid name collision on parts being developed by 
different teams, or to reuse names for objects when the colliding 
unqualified names are more natural (better connected to the concept being 
modelled and implemented).

To make clear the second case above, here is a real example: all tokenizers 
in mcs are called "Tokenizer" (what I think is the most sensible name for 
them) but collision is avoided because each resides in a specific namespace 
(one for each language supported).

And before Rhys asks: MonoBASIC is so called because itīs still partially 
acid, as someone with a dictionary and some chemistry knowledge had pointed 
before...
Maybe he prefers this language variant to be called YogurthBASIC, or 
ZestyBASIC?

Second
Miguel, you asked for an outline. So far what I have identified as possibly 
extension/alternative namespaces are

Mono
  .Languages     // General Compiler classes
    .CSharp      // Specific C# parsing/tokenizing classes
    .MonoBASIC   // Specific VB.NET/MonoBASIC parsing/tokenizing classes
    .Python      // Specific Python parsing/tokenizing classes
  .Runtime
    .LateBind    // General latebinding-support for MonoBASIC/Python
    .MonoBASIC   // Specific runtime classes for MonoBASIC programs
    .Python      // Specific runtime classes for Python programs
  .Web
    .UI
      .Utils     // Gaurav utility classes

And as I said: If ECMA accepts some of our classes, they will find a 
'housing' namespace, and we will promptly move the classes there.

Rafael Teixeira
Brazilian Developer



_________________________________________________________________
Get your FREE download of MSN Explorer at http://explorer.msn.com/intl.asp