Has anyone ever tried to customize memory allocation of field containers? My hope is to address potential memory fragmentation issues resulting from frequent allocation and deallocation of field container objects--assuming that we do find that to be a problem. Specifically, I am thinking about how to change the allocation of custom field containers that are written as extensions to OpenSG. I was skimming the code and started thinking about the possibility of specializing OSG::FieldContainer::newPtr<T>() for a given custom field container type, but maybe it would just be easier (and less arcane) to overload new and delete for the types in question.
Ultimately what I need is an extension point for doing this custom memory allocation that gets along well with the rest of OpenSG. Does anyone have any tips or suggestions? Thanks. -Patrick -- Patrick L. Hartling Senior Software Engineer, Priority 5 http://www.priority5.com/ The information transmitted in this communication is intended only for the person or entity to which it is addressed and contains proprietary material. Any review, retransmission, dissemination or other use of, or taking of any action in reliance upon, this information by persons or entities other than the intended recipient is prohibited. If you received this in error, please destroy any copies, contact the sender and delete the material from any computer. ------------------------------------------------------------------------------ This SF.net email is sponsored by: SourcForge Community SourceForge wants to tell your story. http://p.sf.net/sfu/sf-spreadtheword _______________________________________________ Opensg-users mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/opensg-users
