20,741
edits
Nasal GC Musings: Difference between revisions
Jump to navigation
Jump to search
→concurrent GC
| Line 253: | Line 253: | ||
In the case of FlightGear, implementing a concurrent garbage collector would likely be a significant undertaking and would require a deep understanding of the program's internal workings and how it interacts with Nasal code. It would also require careful design and testing to ensure that the garbage collector does not interfere with the program's execution or cause any performance issues. | In the case of FlightGear, implementing a concurrent garbage collector would likely be a significant undertaking and would require a deep understanding of the program's internal workings and how it interacts with Nasal code. It would also require careful design and testing to ensure that the garbage collector does not interfere with the program's execution or cause any performance issues. | ||
Therefore, while running the garbage collector in a separate thread can improve its performance and reduce its impact on the program, it may not completely eliminate the issue of not being able to execute Nasal code while the garbage collector is running. In order to fully address this issue, a concurrent garbage collector would need to be implemented. | Therefore, while running the garbage collector in a separate thread can improve its performance and reduce its impact on the program, it may not completely eliminate the issue of not being able to execute Nasal code while the garbage collector is running. In order to fully address this issue, a concurrent garbage collector would need to be implemented (or rather, an existing one, being integrated). | ||
== References == | == References == | ||