search

AdityaSantosh / aeroquad

Automatically exported from code.google.com/p/aeroquad
0 stars 0 forks source link

Compiler warnings about no return statement in obsolete functions returning non-void and other FlightAngle.h code clean-up #51

Closed GoogleCodeExporter closed 8 years ago

GoogleCodeExporter commented 8 years ago 
What steps will reproduce the problem?
1. Turn avr-g++ warnings as described here: 
http://www.arduino.cc/cgi-bin/yabb2/YaBB.pl?num=1278712207/6
2. Compile

What is the expected output? What do you see instead?
Expected clean compile, instead seen:

cc1plus: warnings being treated as errors
In file included from AeroQuad.cpp:144:
FlightAngle.h: In member function ‘virtual float 
FlightAngle_CompFilter::getGyroAngle(byte)’:
FlightAngle.h:103: error: no return statement in function returning non-void
FlightAngle.h: In member function ‘virtual float 
FlightAngle_KalmanFilter::getGyroAngle(byte)’:
FlightAngle.h:168: error: no return statement in function returning non-void
FlightAngle.h: In member function ‘void 
FlightAngle_DCM::Drift_correction()’:
FlightAngle.h:421: error: unused variable ‘errorCourse’
FlightAngle.h:422: error: unused variable ‘Scaled_Omega_P’
FlightAngle.h:424: error: unused variable ‘Accel_magnitude’
FlightAngle.h: In member function ‘virtual float 
FlightAngle_MultiWii::getGyroAngle(byte)’:
FlightAngle.h:758: error: no return statement in function returning non-void
In file included from AeroQuad.cpp:227:
Altitude.h: In member function ‘virtual void 
Altitude_AeroQuad_v2::initialize()’:
Altitude.h:154: error: unused variable ‘verifyGroundAltitude’

What version of the product are you using? On what operating system?
Arrduino 0021, Ubuntu 10.10

Please provide any additional information below.
See forum thread:
http://aeroquad.com/showthread.php?1461-We-have-some-hidden-warnings

Attached is the resolution to this issue in two diff files, after applying 
there are no more compiler warnings. We do not use 'getGyroAngle' any more, we 
use 'flightAngle.getData'.

Original issue reported on code.google.com by itodoro...@gmail.com on 1 Dec 2010 at 6:08

Attachments:

GoogleCodeExporter commented 8 years ago 
Done, thanks for the report.

Original comment by CaranchoEngineering@gmail.com on 4 Dec 2010 at 9:35