Details
-
Task
-
Status: To Do
-
Major
-
Resolution: Unresolved
Description
In order to avoid using new/delete in performance-sensitive execution paths, some profiling objects, such as ProfileOperator might be better to use ObjectPool as their memory/object manager
Ideally, this could occur by overloading the new/delete operators in a base class (templated or nor), which would then call ObjectPool.New() and ObjectPool.Delete()