20,741
edits
FGPythonSys: Difference between revisions
Jump to navigation
Jump to search
→Threaded Subysystems
(→Vision) |
|||
| Line 160: | Line 160: | ||
| title = <nowiki>Re: [Flightgear-devel] Designing a thread-safe property tree API | | title = <nowiki>Re: [Flightgear-devel] Designing a thread-safe property tree API | ||
(was Re: A FGPythonSys implementation: ...)</nowiki> | (was Re: A FGPythonSys implementation: ...)</nowiki> | ||
| author = <nowiki>Edward d'Auvergne</nowiki> | |||
| date = Jan 26th, 2016 | |||
| added = Jan 26th, 2016 | |||
| script_version = 0.23 | |||
}} | |||
}} | |||
{{FGCquote | |||
|1= I also had the idea of running this subsystem in a thread. This avoids adding more strain to the main loop, making FGPythonSys even more inconspicuous. And it has downstream benefits, in that I'll be hitting many of the problems often discussed on this mailing list, and hitting them very hard. Asynchronous access to the navdb cache is one such problem. Racing is another - some parts of FlightGear uses SGThreads (such as parts of the sound system). With Python pushing on the code paths prone to racing, with easy to write tests to put huge amounts of strain on the system, I could help improve these parts. I see this as beneficial for the project, even if the Python initiative goes nowhere. | |||
|2= {{cite web | |||
| url = http://sourceforge.net/p/flightgear/mailman/message/34798001/ | |||
| title = <nowiki>Re: [Flightgear-devel] A FGPythonSys implementation: The embedded | |||
Python interpreter as a FlightGear subsystem.</nowiki> | |||
| author = <nowiki>Edward d'Auvergne</nowiki> | | author = <nowiki>Edward d'Auvergne</nowiki> | ||
| date = Jan 26th, 2016 | | date = Jan 26th, 2016 | ||