Load and destroy methods revised for proper reference counting
The update enhances object management by involving scope-based reference counting. The change affects loading and destruction operations in the Object and several other classes, ensuring the release or retention of objects adhere to their usage context. A function for logging type data has also been introduced to provide better clarity during debugging. Also, tests in script & interpreter have been altered to run in separate module initializations to avoid cross-test interference. Overall, it provides better memory management and dependable tests.
This commit is contained in:
parent
b06e1da529
commit
55571ca3dd
12 changed files with 58 additions and 10 deletions
|
|
@ -18,12 +18,19 @@ int main() {
|
|||
tp::ModuleManifest module("ObjectsTests", nullptr, nullptr, deps);
|
||||
|
||||
if (module.initialize()) {
|
||||
|
||||
testCore();
|
||||
testPrimitives();
|
||||
testInterpreter();
|
||||
|
||||
module.deinitialize();
|
||||
}
|
||||
|
||||
if (module.initialize()) {
|
||||
testPrimitives();
|
||||
module.deinitialize();
|
||||
}
|
||||
|
||||
if (module.initialize()) {
|
||||
testInterpreter();
|
||||
module.deinitialize();
|
||||
}
|
||||
|
||||
return 0;
|
||||
}
|
||||
Loading…
Add table
Add a link
Reference in a new issue