Re: [gobo-eiffel-develop] [Es-devel] .NET namespace configuration

[Eric B. <er...@go...>]

Emmanuel Stapf [ES] wrote:
>> Our non-Eiffel code will break when we move to 6.0, but the 
>> fix is an easy, one-off search-and-replace operation. A few 
>> class names changed already in 5.7. (Speaking of which, I'm 
>> using an ugly override-and-alias hack to rename
>> STRING_8 and INTEGER_32 back to STRING and INTEGER for our 
>> non-Eiffel consumers. Does 6.0 allow us to do this purely 
>> within the ECF?)
> 
> Unfortunately it does not. This would go against the above principle that says
> that a library is fully in control of its namespace.
>  
>> My only quibble with your proposal is the name 
>> EiffelSoftware.Library. I would have expected:
>>     EiffelSoftware.Base
>>     EiffelSoftware.Vision
>>     EiffelSoftware.Wel
> 
> See Paul's anser on the subject.
> 
>> Yes, gobo.ecf specifies the EiffelSoftware.Library namespace!
> 
> This is the result of a blind addition of namespace to all our ECFs. I'll check
> with Eric what he would like.

I'm not a .NET user, so I don't have an opinion.
Perhaps people on the Gobo mailing lists have one.
The context of this discussion is here:

  http://www.nabble.com/.NET-namespace-configuration-tf3428939.html

and 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
    ...

-- 
Eric Bezault
mailto:er...@go...
http://www.gobosoft.com