Re: Some issues with the codebase

[taraben . a]

 Chad Yates wrote:

> ...
>
> My personal opinion is they shouldn't be used period. and if they must, then
> only as a word separator.  I'm also of the opinion that cryptic
> abbreviations should not be used, especially in external api's.
+1  from my side.

> I also like the "java" style with infix caps except the first word (ie.
> getMyProperty, setMyProperty, doSomething, isActive...) and then classes
> using plain infix caps (i.e. Digest, Thread, CRCDigest...)  for the most
but then how do you differ between class and instance.

> part the areas I have used in common c++ seem to already be using that
> style, except for a there are some places that use 'doSomething', and others
> that use 'DoSomething'.  It would be nice to come up with a style guide for
> all new code, and then slowly move the existing code that is out of spec
> into spec deprecating the old method names, and at some point (say a major
> release) removing them.
>  
In my opinion there should be a clear difference in between type, 
instance, constant, method (do,get,set), local or privat member member, 
global variable. Did I miss something?

> ...
>
> on this, I think it makes sense to have a namespace carved out for the
> product itself, since it is a library.  I'm not sure what ccxx is supposed
> to mean (x's just placeholders for whatever?) but something that relates to
> the lib would make sense.  I can see the bayonne project (is that an open
> source telecom product?) using an ost namespace and any other ost specific
> applications.  It's all a matter of preference, but when I first saw a
> 'using ost' declaration I had no clue what it meant.  cppunit uses cppunit
> and the standard C++ lib uses std.  Perhaps having a vendor neutral
> namespace would discourage bantering if and when (and I hope it happens)
> there are more vendors contributing substantial parts to common c++.  too me
> its not that big of a deal.  just my 2 cents and opinion.
>
> cheers,
>
> Chad
>
>  
why not simple using comm ?? placeholder for common c++ or communication :-)

I think this is a very esotheric issue and so many different opinions 
around ... so sorry for bugging you ;-)

Adib.