842
edits
FlightGear Newsletter November 2018: Difference between revisions
Jump to navigation
Jump to search
FlightGear Newsletter November 2018 (view source)
Revision as of 13:55, 30 November 2018
, 30 November 2018→Development news
Legoboyvdlp (talk | contribs) |
Legoboyvdlp (talk | contribs) |
||
| Line 29: | Line 29: | ||
== Development news == | == Development news == | ||
<!-- News about FlightGear itself. The FlightGear mailing list and/or core developers are a good source. --> | <!-- News about FlightGear itself. The FlightGear mailing list and/or core developers are a good source. --> | ||
=== Stricter JSBSIM tag checking === | |||
{{cquote|Hi all, | |||
since the change to the parser, JSBSim is not only a lot more verbose | |||
about issues (good!) but also a lot more picky about accepting | |||
syntactically bad tags (somewhat problematic). | |||
The implication is that this is again a change that will render aircraft | |||
which previously worked okay non-functional on next - so an unknown | |||
fraction of our JSBSim fleet currently won't start. | |||
(And yes, I've seen issues in someone else's code, so it's not only my | |||
sloppy habits ;-) ) | |||
The good news is that we get explicit locations for the offending tags | |||
including line numbers, so generally the issues are easy to fix. Also, | |||
these are tags which never worked as intended in the first place, so | |||
fixing them to a working condition is likely easy. | |||
My recommendation is that anyone who sees such issues on the repo simply | |||
goes ahead and pushes a fix if he has commit rights. If not, or if you | |||
feel unsure because you have no experience with JSBSim, give me a note | |||
with the errors and I'll go ahead and do the maintenance. | |||
|Thorsten}} | |||
== New software tools and projects == | == New software tools and projects == | ||