20,741
edits
Modernizing FlightGear Scripting: Difference between revisions
Jump to navigation
Jump to search
Modernizing FlightGear Scripting (view source)
Revision as of 14:08, 8 October 2016
, 8 October 2016→On replacing Nasal
| Line 269: | Line 269: | ||
|date = Feb 26th, 2009 | |date = Feb 26th, 2009 | ||
|added = Feb 26th, 2009 | |added = Feb 26th, 2009 | ||
|script_version = 0.40 | |||
}}</ref> | |||
Most developers would prefer we have /one/, and only one scripting language in Flightgear and would be be delighted for that to be a better supported, more widely used language than Nasal, but we don’t want to end up with multiple scripting languages co-existing. I.e if we’re going down the Python route, we need a coherent plan, even if it takes two years, to phase out Nasal. <ref>{{cite web | |||
|url = https://sourceforge.net/p/flightgear/mailman/message/34790212/ | |||
|title = <nowiki> Re: [Flightgear-devel] A FGPythonSys implementation: The embedded | |||
Python interpreter as a FlightGear subsystem. </nowiki> | |||
|author = <nowiki> James Turner </nowiki> | |||
|date = Jan 23rd, 2016 | |||
|added = Jan 23rd, 2016 | |||
|script_version = 0.40 | |script_version = 0.40 | ||
}}</ref> | }}</ref> | ||