DOM memory system: Difference between revisions
Jump to navigation
Jump to search
a little formatting to make it easier to grok |
catg up a level |
||
| Line 11: | Line 11: | ||
{{DOM navigation}} | {{DOM navigation}} | ||
[[Category:DOM | [[Category:COLLADA DOM|Memory system]] | ||
Revision as of 00:52, 31 May 2007
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 |