![]() Come to think of it, even if an app knows to call getLatitude/Longitude on GeoPoint so that it's fully constructed, it has no way to do so on any use of GeoPoint embedded within other Geo3d shapes (such as GeoDegenerateHorizontalLine). This isn't necessarily a big deal but at least should be documented for these two classes, indicating how to construct them such that they are thread-safe. Lazy BBox calculation of Geo3dShape is another reason. There should be some docs/language somewhere so that people can understand that Geo3D generally isn't necessarily threadsafe, and GeoPoint in particular isn't. The issue of thread-safety came to mind as I saw the lazy-evaluation of the latitude & longitude. And for that matter, GeoPoint.arcDistance could mention it's computation is surface of a sphere, and that for accurate ellipsoidal, use PlanetModel.surfaceDistance().
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |