Re: [Es-devel] .NET namespace configuration

Eric Bezault wrote:
> ... namespace suggested by Manu for the Gobo libraries is
> Gobosoft.Library.Gobo.
>
> We should perhaps take into account that Gobo is not just
> one library, despite what the gobo.ecf file provided by ISE
> may tend to imply. And Gobosoft is an artifact to get a
> domain name because gobo.com/gobo.org were already used.
> So what about:
>
>    Gobo.Library.Structure
>    Gobo.Library.XML
>    Gobo.Library.Time
>    ...

This would be achieved by adding this option to gobo.ecf:

    <option namespace="Gobo.Library"/>

The end result would be subclusters getting appended automatically, due to 
UCNN (use cluster name as namespace) and URCNN (use recursive cluster name 
as namespace) both being True by default. Given the other settings in the 
current gobo.ecf (EiffelStudio 6.0.6.7358), we would see these namespaces:
    Gobo.Library.GoboStructure
    Gobo.Library.GoboXml
    Gobo.Library.GoboTime

This is almost what you suggested, Eric, with two differences:

1. The redundant "Gobo" in the last part of each namespace is caused by the 
"gobo_" prefixes on the cluster names. I don't know why they've done this; I 
don't see any risk of a clash of cluster names, given EiffelStudio's new 
library mechanism. I think the redundant prefix should be dropped.

2. "Xml" rather than "XML". The .NET naming convention is that where an 
acronym is longer than two letters, only the first letter should be upper 
case.

So I think the current state of gobo.ecf is fine, with two changes:
1. <option namespace="Gobo.Library"/>
2. Drop the "gobo_" prefixes.

- Peter Gummer