70
edits
Bugs: Difference between revisions
Jump to navigation
Jump to search
Misdirected diagnostic in JSBSim.cxx
John Denker (talk | contribs) mNo edit summary |
John Denker (talk | contribs) (Misdirected diagnostic in JSBSim.cxx) |
||
| Line 393: | Line 393: | ||
with hardware acceleration. As a point of reference, | with hardware acceleration. As a point of reference, | ||
glxgears uses only a fraction of one percent of the cpu. | glxgears uses only a fraction of one percent of the cpu. | ||
==== Misdirected diagnostic in JSBSim.cxx ==== | |||
The file JSBSim.cxx contains the following code: | |||
if (!cache_ok) { | |||
SG_LOG(SG_FLIGHT, SG_WARN, | |||
"FGInterface is being called without scenery below the aircraft!"); | |||
cout << "altitude = " << alt << endl; | |||
cout << "sea level radius = " << slr << endl; | |||
cout << "latitude = " << lat << endl; | |||
cout << "longitude = " << lon << endl; | |||
//return; | |||
} | |||
Apparently this "ought" to be a five-line diagnostic message. | |||
In fact, the first line is directed to the SG_LOG at priority SG_WARN, | |||
while the other four lines are directed to cout regardless of | |||
priority. This makes both the log and the console record hard | |||
to interpret. | |||
== Missing Features and Traps for the Unwary == | == Missing Features and Traps for the Unwary == | ||