On 2015-12-01 15:34, Martin Walch wrote:
On Saturday, November 14, 2015 06:08:55 PM Alex Merry wrote:
On 2015-11-14 01:21, Martin Walch wrote:
> Alright, so I have created a stub at
>
> https://techbase.kde.org/Policies/Frameworks_Coding_Style
>
> ...
>
> Qt includes
> * For Qt #includes omit the module name and only use the class name.
These are all still applicable.
Does the same pattern apply to Frameworks includes?
For example:
KFileItem instead of KIOCore/KFileItem
and
KIO/HostInfo instead of KIOCore/KIO/HostInfo
and of course not something like kfileitem.h or kio/hostinfo.h
Yes, although good luck trying to explain that, given the inconsistency
between <KIO/HostInfo> and <KFileItem>. <KIOCore/KFileItem> is only
possible by fluke, really, as a side effect of where we install the
version headers.
Alex
_______________________________________________
Kde-frameworks-devel mailing list
Kde-frameworks-devel@kde.org
https://mail.kde.org/mailman/listinfo/kde-frameworks-devel