Skip to content
This repository has been archived by the owner on May 29, 2022. It is now read-only.

Allow client-code to treat SatPass as constant #15

Open
wants to merge 15 commits into
base: master
Choose a base branch
from

Conversation

rwpenney
Copy link
Contributor

@rwpenney rwpenney commented Sep 2, 2016

Various methods within SatPass have changed since gpstk-2.6 which break client code which attempts to treat SatPass as a constant. Query methods like data() force the client to receive a non-constant reference even when they need read-only access to observation data.
Various patches have been added to SatPass which improve support for read-only access by clients using "const SatPass" objects. Also, various getter methods have been adjusted to take const std::string& to avoid unnecessary copying of string parameters that are not modified within GPSTk.

rwpenney and others added 9 commits September 2, 2016 16:50
Avoided unnecessary copying of std::strings passed to getter methods.
Improved support for treating SatPass objects as constants in client code.
Centralized out-of-bounds logic in SatPass getter/setter methods.
Added typedef for index/label std::map types.
Simplified copying of std::vectors within SatPassData.
Removed various unused variables.
Reordered various constructor member initializers.
Reduced usage of clang-specific #pragmas.
Temporarily set umask to 000 when checking FileUtils::makeDir().
Fixed various signed/unsigned mismatches etc.
Removed various redundant empty return statements.
Removed unused (duplicated) time-printing shortcut() function.
Patched various uninitialized variables and signed/unsigned mismatches.
@rwpenney
Copy link
Contributor Author

Branch now updated to track upstream GPSTk-2.10

@masamitsutech
Copy link
Contributor

Before this pull request can be reviewed for the next stable release, please update the branch to resolve possible merge conflicts.

@rwpenney
Copy link
Contributor Author

rwpenney commented Oct 6, 2018

I've updated this branch to mirror gpstk-2.10.6, but the PRSolve_Rinexout test is failing. It's not obvious that this has anything to do with the changes I've been making. I suspect the issue is some form of counting error near line 340 of PRSolution.cpp where the indexing of the CRange and SVP arrays gets out of sync.

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants