>>>>> "Roman" == Roman Kennke <[EMAIL PROTECTED]> writes:
Roman> That would most likely cause problems on these ports. The specific
Roman> problem is that these ports actually have a malloc() syscall, only that
Roman> it doesn't really do what you would expect, and the macro works around
Roman> that by calling another (platform specific) syscall that does what's
Roman> expected. The best thing I can offer is a shorter macro name.
You can always:
#undef malloc
#define malloc SomethingElse
It is unlikely that this is going to break something.
Roman> I am aware of that problem. Still I don't know how to solve that
Roman> problem. We simply cannot give away some of our ports, due to license
Roman> and other restrictions.
The macro idea is one way... it puts the cost on the targets, not on
Classpath.
Tom
_______________________________________________
Classpath-patches mailing list
[email protected]
http://lists.gnu.org/mailman/listinfo/classpath-patches
