Header files (Re: A little review of kdecore & kdeui)

[Aaron J. Seigo]

On Saturday 08 April 2006 03:10, André Wöbbeking wrote:
> Is it really easier?

after working with Qt4 for a while now, my experience says "yes, it's easier, 
though only marginally".

you just #include <ClassName>, exactly as you type it when doing "new 
ClassName". no more having to remember which header contains the class (think 
qlayout.h) and makes it rather obvious what classes are being used in the 
file.

it certainly doesn't have a negative effect, so i don't see the problem. the 
only arguments i've seen are optimizing for clumsy win32 developers (which we 
don't have and which are easy to address once we do) and that some tools 
don't like files w/out extensions (time to update your tools; it's the 21st 
century already ;)

-- 
Aaron J. Seigo
GPG Fingerprint: 8B8B 2209 0C6F 7C47 B1EA  EE75 D6B7 2EB1 A7F1 DB43

Full time KDE developer sponsored by Trolltech (http://www.trolltech.com)
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 189 bytes
Desc: not available
URL: <http://mail.kde.org/pipermail/kde-core-devel/attachments/20060408/c775afc7/attachment.sig>