Re: [Texmacs-dev] "Overloading ambiguity" error in compiling 1.0.7.2

[David Allouche]

On Thu, Jun 18, 2009 at 19:23, Joris van der Hoeven <address@hidden> wrot
>
> Very annoying. I hope this is the only occurrence of this problem.
> This is due to f****** C++; I did not find a clean way to redefine
> the new operator for TeXmacs objects only (avoiding interaction with Qt).
> I had to explicitly list all cases of tm_new in fast_alloc.hpp.
>
> You may try to disambiguate by casting the first argument to
> const list<int>& and see if that works. You may also try to
> add additional tm_new forms in fast_alloc.hpp.
> Please play a bit and tell me what works for you.

I assume you are aware that you can redefine operator new as a
*method* in the classes that you want to use your custom allocator.
Typically, you would put the overloaded new in some foundation class.

It seems to me, this language feature allows you to exactly "redefine
the new operator for TeXmacs objects only (avoiding interaction with
Qt)".