Template:Leaking Nasal disclaimer: Difference between revisions
Jump to navigation
Jump to search
m (cat) |
mNo edit summary |
||
Line 1: | Line 1: | ||
{{caution|Using the <code>{{{oldapi|foo}}}</code> API, it is fairly easy to leak resources by not using the API properly. This happens typically by not keeping track of how many callbacks (or loops) are registered to be invoked/running by a certain timer/listener. Equally, [[Reset & re-init]] handling is often not | {{caution|Using the <code>{{{oldapi|foo}}}</code> API, it is fairly easy to leak resources by not using the API properly. This happens typically by not keeping track of how many callbacks (or loops) are registered to be invoked/running by a certain timer/listener. Equally, [[Reset & re-init]] handling is often not done properly by such low-level code because listeners and timers need to be manually tracked/managed. These days, it is generally recommended to favor the <code>{{{newapi|bar}}}</code> API instead. Alternatively, you should consider wrapping the low-level APIs using a helper class, which is also the recommended way for supporting multiple different FlightGear binaries.}} | ||
<noinclude> | <noinclude> | ||
[[Category:Templates]] | [[Category:Templates]] | ||
[[Category:Undocumented templates]] | [[Category:Undocumented templates]] | ||
</noinclude> | </noinclude> |
Revision as of 15:48, 9 January 2015
Caution Using the foo API, it is fairly easy to leak resources by not using the API properly. This happens typically by not keeping track of how many callbacks (or loops) are registered to be invoked/running by a certain timer/listener. Equally, Reset & re-init handling is often not done properly by such low-level code because listeners and timers need to be manually tracked/managed. These days, it is generally recommended to favor the bar API instead. Alternatively, you should consider wrapping the low-level APIs using a helper class, which is also the recommended way for supporting multiple different FlightGear binaries.
|