Modernizing FlightGear Scripting: Difference between revisions

Jump to navigation Jump to search
Line 273: Line 273:


== Challenges ==
== Challenges ==
porting several hundred thousand lines of Nasal to something else, even if it is automated to a high degree, doesn't sound very attractive..<ref>{{cite web
  |url    =  https://sourceforge.net/p/flightgear/mailman/message/34791061/
  |title  =  <nowiki> Re: [Flightgear-devel] A FGPythonSys implementation: The embedded
Python interpreter as a FlightGear subsystem. </nowiki>
  |author =  <nowiki> Anton Gomez Alvedro </nowiki>
  |date  =  Jan 24th, 2016
  |added  =  Jan 24th, 2016
  |script_version = 0.40
  }}</ref>
The paradigm of binding a C/C++ core to a scripting language has its own disadvantages, and that makes it very difficult to switch.<ref>{{cite web
The paradigm of binding a C/C++ core to a scripting language has its own disadvantages, and that makes it very difficult to switch.<ref>{{cite web
   |url    =  https://forum.flightgear.org/viewtopic.php?p=296201#p296201  
   |url    =  https://forum.flightgear.org/viewtopic.php?p=296201#p296201  

Navigation menu