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

List:       kde-core-devel
Subject:    K*Base -> KAbstract*
From:       Andreas Hartmetz <ahartmetz () gmail ! com>
Date:       2007-03-17 1:32:24
Message-ID: 200703170232.24757.ahartmetz () gmail ! com
[Download RAW message or body]

Hi!

I think we should change the naming conventions of abstract base classes in 
kdelibs and kdebaes, too, if applicable. Naming conventions for pure virtual 
classes are pretty arbitrary, I guess, but now we have precedents in Qt that 
we should follow.
I also find ...Base somewhat confusing. Without knowing the convention, it 
sounds like "this is the basic functionality (that you can actually 
instantiate and use)". The documentation finally told me what it means when I 
read it, which is too late considering that people read code all the time 
without knowing all of the documentation.
I'd like to commit changes on monday.
Do we all agree that clarity beats brevity?

Regards,
Andreas
[prev in list] [next in list] [prev in thread] [next in thread]