AP_Mission: avoid using struct Location

clang reports this could be a problem when compiling under some EABIs.  Remove it from most places as it is just noise, replace with class where we want to avoid including Location.h
This commit is contained in:
Peter Barker 2023-02-03 09:58:39 +11:00 committed by Peter Barker
parent 5c262144f0
commit 03f5c321b0
2 changed files with 3 additions and 3 deletions

View File

@ -2118,7 +2118,7 @@ uint16_t AP_Mission::num_commands_max(void) const
// be found.
uint16_t AP_Mission::get_landing_sequence_start()
{
struct Location current_loc;
Location current_loc;
if (!AP::ahrs().get_location(current_loc)) {
return 0;
@ -2186,7 +2186,7 @@ bool AP_Mission::jump_to_landing_sequence(void)
// jumps the mission to the closest landing abort that is planned, returns false if unable to find a valid abort
bool AP_Mission::jump_to_abort_landing_sequence(void)
{
struct Location current_loc;
Location current_loc;
uint16_t abort_index = 0;
if (AP::ahrs().get_location(current_loc)) {

View File

@ -769,7 +769,7 @@ private:
uint16_t _prev_nav_cmd_id; // id of the previous "navigation" command. (WAYPOINT, LOITER_TO_ALT, ect etc)
uint16_t _prev_nav_cmd_index; // index of the previous "navigation" command. Rarely used which is why we don't store the whole command
uint16_t _prev_nav_cmd_wp_index; // index of the previous "navigation" command that contains a waypoint. Rarely used which is why we don't store the whole command
struct Location _exit_position; // the position in the mission that the mission was exited
Location _exit_position; // the position in the mission that the mission was exited
// jump related variables
struct jump_tracking_struct {