DUChain support of defaulted/deleted functions again

[Niko Sams]

On Sun, Jun 19, 2011 at 20:38, Milian Wolff <mail at milianw.de> wrote:
>> > I just don't know whether putting it directly into Declaration is a good
>> > place. For one thing this is a pure C++0x feature, I don't know of any
>> > other language with a similar feature. To make matters worse only
>> > FunctionDeclarations can be deleted in C++0x... If preferred I could
>> > simply create a CppFunctionDeclaration that also tracks the
>> > isSignal/isSlot and thus cleans our API a bit of Cpp-Isms...
>>
>> In GCC's language-independent internal representation of functions and
>> similar things, they store some information in "lang_flags" -- essentially
>> bits in their data structures that are interpreted differently by
>> different language front ends. They have a generic name, and are accessed
>> by (global, not member) functions in the front end that are named to
>> indicate what the meaning of this generically named flag is in the
>> language front end currently in use.
>
> Well thanks, but imo this does not apply to KDevelop. We can have language
> dependent declarations and types and use that already where applicable. But
> since Cpp was the crash-test-dummy for developing the biggest part of the
> DUChain API there are some cpp-isms left-over.
>
> Anyways, I'd like to hear the feedback from KDevplatform API users and
> developers on where you want me to put the above discussed feature :)
Imho it makes sense to have that in a CppFunctionDeclaration as it's cpp only.

Niko