DOM memory system: Difference between revisions
Jump to navigation
Jump to search
No edit summary |
No edit summary |
||
| (7 intermediate revisions by 2 users not shown) | |||
| Line 1: | Line 1: | ||
Internal notes on the '''[[COLLADA DOM]] memory system''' | '''Summary:''' Internal notes on the '''[[COLLADA DOM]] memory system'''. | ||
''' | '''Purpose:''' The <code>daeMemory</code> system is supposed to be a class that manages the [[COLLADA DOM]]'s memory from different heap pools: | ||
It overwrites | * It overwrites <code>malloc</code> and <code>free</code>. | ||
All dae classes overwrite | * All dae classes overwrite <code>new</code> and <code>delete</code> to use the <code>daeMemorySystem</code>'s <code>malloc</code> and <code>free</code>. | ||
This has never been fully implemented. It actually makes it harder to profile the DOM because many memory profilers replace | This has never been fully implemented. It actually makes it harder to profile the DOM because many memory profilers replace <code>new/delete</code> and <code>malloc/free</code> with their own functions but, since the DOM does that also, they don’t work. | ||
[[Category:DOM | {{DOM navigation}} | ||
[[Category:COLLADA DOM|Memory system]] | |||
Latest revision as of 23:49, 6 February 2008
Summary: Internal notes on the COLLADA DOM memory system.
Purpose: The daeMemory system is supposed to be a class that manages the COLLADA DOM's memory from different heap pools:
- It overwrites
mallocandfree.
- All dae classes overwrite
newanddeleteto use thedaeMemorySystem'smallocandfree.
This has never been fully implemented. It actually makes it harder to profile the DOM because many memory profilers replace new/delete and malloc/free with their own functions but, since the DOM does that also, they don’t work.
| COLLADA DOM - Version 2.4 Historical Reference |
|---|
| List of main articles under the DOM portal. |
| User Guide chapters: • Intro • Architecture • Setting up • Working with documents • Creating docs • Importing docs • Representing elements • Working with elements • Resolving URIs • Resolving SIDs • Using custom COLLADA data • Integration templates • Error handling Systems: • URI resolver • Meta • Load/save flow • Runtime database • Memory • StringRef • Code generator |