-
Notifications
You must be signed in to change notification settings - Fork 24
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
* Per issue #1899, changed the main storage array (double * e) to vector<double> e. Modifying functions accordingly. SL * Per issue #1899: removed commented out code. Still in progress. SL * Per issue #1899: modified more functions to use vector or vector functions instead of arrays. In progress. SL * Per issue #1899: updated add() functions to use push_back to add values to vector. SL * Per #1899, correct logic in NumArray::init_from_scratch() to call NumArray::clear() instead of vector::clear(). * Per issue #1899: added some temporary print statements for debugging. SL * Per issue #1899: added some more temporary print statements for debugging. In progress. SL * Per issue #1899: added some temporary print statements for debugging. In progress. SL * Per issue #1899: replaced Nelements with n_elements(). SL * Per issue #1899: modified extend function some more for using vectors. In progres. SL * Per issue #1899: continued to modify some functions for using a base vector for storage (instead of array). In progress. SL * Per issue #1899: removed / added a few temporary print statements for debugging. SL * Per #1899, this change seems to clearly be a bug. We should be using tc_poly_array_alloc_inc instead of num_array_alloc_inc in tc_poly.cc. * Per issue #1899: commented out some print statements for now. For running make test. SL * Per #1899, updating NumArray class to use STL::vector. * Per #1899, I removed the exact option from NumArray::extend() since after switching to STL::vector, it'll ALWAYS be an exact allocation. Previously, we always rounded up to the next allocation increment, but there's no allocation increment anymore. Updating the other code to removes calls to exact. * Per #1899, removing debug cout statements. * Per #1899, cleaning up one leftover debug cout line. * Per issue #1899: updated the erase() funciton to use vector.clear() and vector.reserve(). SL * Per issue: #1899, cleaned up clear() and erase() functions. SL Co-authored-by: Seth Linden <linden@kiowa.rap.ucar.edu> Co-authored-by: John Halley Gotway <johnhg@ucar.edu>
- Loading branch information
1 parent
77f38b3
commit 2afeb79
Showing
9 changed files
with
457 additions
and
527 deletions.
There are no files selected for viewing
Large diffs are not rendered by default.
Oops, something went wrong.
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters