Options to fix iPhoneMemory new operator redefinition error
by Marc Dreamora Schaerer · in iTorque 2D · 07/12/2009 (8:08 am) · 0 replies
I wanted to check if others are like me on the way to get rid of the new operator override that happens in iphonememory.
The override there is actually impacting the interoperability of iTGB with other iphone systems significantly.
Various 3rd party libraries can not work with iTGB in the project due to it, as it conflicts with GCCs own new operator used and expected by other source systems as it redefines it.
OpenFeint is the newest victim of this "smart overload of standard platform functionality", making it impossible to have it in as it will fail.
I assume the simplest solution is to attempt the fix starting with constructInPlace in platform.h as it is the major source where this new operator is beeing used?
Any other usable options that don't force deeper modifications?
Its kind of a shame that the engine is not only not really targeted at the iphone but that it also actively works against embedding standard 3rd party technology with it.
I'm starting to really consider Cocos2D + Tiled for my project as it even at worst can't be as much work as it is to get iTGB to work nicely, fast and platform compliant and that although Cocos2D costs $0, not $750 like "i"TGB
The override there is actually impacting the interoperability of iTGB with other iphone systems significantly.
Various 3rd party libraries can not work with iTGB in the project due to it, as it conflicts with GCCs own new operator used and expected by other source systems as it redefines it.
OpenFeint is the newest victim of this "smart overload of standard platform functionality", making it impossible to have it in as it will fail.
I assume the simplest solution is to attempt the fix starting with constructInPlace in platform.h as it is the major source where this new operator is beeing used?
Any other usable options that don't force deeper modifications?
Its kind of a shame that the engine is not only not really targeted at the iphone but that it also actively works against embedding standard 3rd party technology with it.
I'm starting to really consider Cocos2D + Tiled for my project as it even at worst can't be as much work as it is to get iTGB to work nicely, fast and platform compliant and that although Cocos2D costs $0, not $750 like "i"TGB
About the author
