New i18n interface for KDE 4

[Nicolas Goutte]

On Sunday 11 September 2005 15:51, Chusslove Illich wrote:
> > [: Nicolas Goutte :]
> > There is a (big) difference about creating clear member functions and
> > about tweaking with vital functions of a class in a way that is not
> > guaranteed to be supported by all C++ compilers.
> >
> > (But I will not be the one who will maintain it. I just want to avoid
> > you a potential nightmare. But as my father often used to say:
> > "Experience cannot be transmitted.")
>
> I don't see much of a maintenance problem just because of overloaded
> operator new. It is a standard language feature, and configure time check
> can find out if compiler is broken. If it is, then on that platform
> operator new simply will not be overloaded.
>
> GCC 3 and 4 can overload new, I expect that modern Windows compilers can
> also do it, so the systems with broken compilers on which KDE can be
> compiled, will be minor. The probability of someone developing KDE code on
> such a system *and* dynamically allocating KI18n is very, very small. And
> if it happens, such code will not compile on majority of platforms.

But we have here a new key class of KDE, not one that you can skip easily. So 
if the compiler fails, it means that you cannot port KDE to that compiler 
(and I am not meaning MS Windows in that case.)

>
(...)

Have a nice day!