HwyVec nomenclature is used in highway.cpp itself, and canvas.cpp. Be consistent!
HwyList name was only retained to keep a commit DIFF more human-readable. This is done.
SysList -> SysDeq in canvas.cpp, similarly
OrigLat, OrigLon -> Lat, Lon
waypoint, highway, wpquadtree, canvas, gisplunge
Reduced confusion & clutter and better readability in most programs outweighs the slight advantage of disambiguation from OffLat, OffLon, OnLat, OnLon in the context of gisplunge. Simple Lat & Lon will be fine here.
cmp -> other in tmsystem.cpp
I never particularly liked "cmp"; just had to call it something
"other" is a bit more intuitive, and matches the new waypoint::nearby function, copped from Jim's siteupdate.py
scrap highway::ListPts
I could remove std::cout.precision(9); and use to_string instead, but...
This debug function has outlived its usefulness. (The //*/ after the closing brace is telling.) Its purpose can be just as easily, and more usefully, accomplished by using highway::write.
HwyList -> HwyVec in gisplunge.cpp
HwyVecnomenclature is used in highway.cpp itself, and canvas.cpp. Be consistent!HwyListname was only retained to keep a commit DIFF more human-readable. This is done.SysList -> SysDeq in canvas.cpp, similarly
OrigLat, OrigLon -> Lat, Lon
cmp -> other in tmsystem.cpp
scrap highway::ListPts
std::cout.precision(9);and useto_stringinstead, but...//*/after the closing brace is telling.) Its purpose can be just as easily, and more usefully, accomplished by using highway::write.gisplunge.cpp: nix
//hwy->ListPts(0);