[prev in list] [next in list] [prev in thread] [next in thread] 

List:       activemq-dev
Subject:    Re: Regarding feedback on OpenWire C++ client
From:       "Hiram Chirino" <hiram () hiramchirino ! com>
Date:       2006-03-28 16:18:03
Message-ID: af2843cd0603280818g1816218ck803e2facaa37e38f () mail ! gmail ! com
[Download RAW message or body]

On 3/28/06, Mats Forslöf <Mats.Forslof@portwise.com> wrote:
> Hi Hiram,
> 
> 
> Even so it might be better to be a bit overzealous to prevent namespace clashes :)
> 

I would like to make this c++ lib, feel very c++ like, I don't want it
to smell like it came from a Java shop.  So I think it's better to
have short names like most of the other libs out there.

> If ASF does not have any rules about this we'll change it - no problem. However, if \
> we're to sync the names between C# and C++ the C# name spaces should be altered \
> also!? 
> C#
> namespace cms
> namespace activemq.command
> namespace activemq.core
> namespace activemq.io
> 


No.. becaue the C# one alos works for VB.NET and J# etc. etc. that's
why the interface are in the .NET Message Service (NMS) namespace. 
Also .Net uses Camel case convention in it's namespaces.  So we will
do it like that.  Once again the aim is to have a .NET library the
feels very native.


> C++
> namespace cms
> namespace activemq::command
> namespace activemq::io
> namespace activemq::marshal
> namespace activemq::protocol
> namespace activemq::transport
> namespace activemq::util
> 

This looks good to me!

> Regards,
> Mats
> 


--
Regards,
Hiram


[prev in list] [next in list] [prev in thread] [next in thread]