Actually, from my perspective overloading malloc is a constant source of pain. This makes developers fighting malloc implementation, instead of writing algorithms.
I would prefer Singular not doing so and I hope, that Sage doesn't follow our bad example. I think, the problem omalloc solves would be tackled better by the explicit use of a pool, where it is needed. Michael P.S.: Did you know, that when overloading the "new operator" in C++, there are two signatures for it: one for new with exception support and one without. Imagine, what happens, when overload the wrong one (essentially you don't overload new) and overload delete correctly. --~--~---------~--~----~------------~-------~--~----~ To post to this group, send email to sage-devel@googlegroups.com To unsubscribe from this group, send email to sage-devel-unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/sage-devel URLs: http://www.sagemath.org -~----------~----~----~----~------~----~------~--~---
