ClassFunctionDeclaration: Cpp specificas? (Defaulted/Deleted or Signal/Slot)

Milian Wolff mail at milianw.de
Fri Jun 17 23:45:14 UTC 2011


On Saturday 18 June 2011 00:58:00 Milian Wolff wrote:
> Hey all, esp. David ;-)
> 
> I have a patch locally that properly tracks default/deleted flag in the
> DUChain, similar to AbstractFunctionFlag or Signal/Slot in
> ClassFunctionDeclaration.
> 
> But I wonder: Both defaulted/deleted and signal/slot are (imo?) Cpp
> specific - should we still put it in the global language agnostic API?
> 
> The reason I did it this way for now is that it does not have any overhead,
> i.e. we have the ClassFunctionFlags anyways and storing an additional
> 
> Though from a API pov this looks rather unclean to me - what do you think?
> 
> Considering that there is already a QtFunctionDeclaration which should
> store the sig/slot stuff, we can have a specific-to-C++
> ClassFunctionDeclaration that also tracks defaulted/deleted flag and
> others as required?

I've pushed the changes to kdevplatform/master and kdevelop/c++0x for review.

bye
-- 
Milian Wolff
mail at milianw.de
http://milianw.de
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 198 bytes
Desc: This is a digitally signed message part.
URL: <http://mail.kde.org/pipermail/kdevelop-devel/attachments/20110618/c28f8a2c/attachment.sig>


More information about the KDevelop-devel mailing list