header policy question

[Raphael Kubo da Costa]

At Fri, 22 Oct 2010 19:40:40 -0400,
Evan Teran wrote:
> 
> One thing I've noticed in the kcalc source is the usage of things like
> #include <stdlib.h> as opposed to #include <cstdlib>.
> 
> I remember a long time ago someone told me this was for portability
> reasons. Makes sense, I figure there has to be some platform out there
> that KDE supports that doesn't have a compliant compiler.
> 
> But then I noticed during my recent work sporadic usage of the c++
> convention.  So my question is, is this compatability argument out of
> date? Does KDE have a policy with regard to using the c++ style
> headers for the legacy c headers?

I can't recall such policy off the top of my head, but if there's one
you can find it somewhere in http://techbase.kde.org/Policies.

I for one would rather use <cstdlib>. You can also take this to
kde-devel@ (or -core-devel) to see if someone has any strong opinion
on the matter.