From: s duclos <sylvain_duclos@ya...> - 2009-04-16 15:41:05
The story is that it was set to use 'double' instead of 'float' when
handling coordinate inside GV.
Originally it was set to sidestep the implicit type conversion from
double <--> float that occur between GV / OGR and GV / PROJ.
It turn out that it make no discernible difference whether on or not
(as far as I can tell.)
This switch is require for the S52 plug-in as everything is in
double on the S52 side and S52 use GV coordinate "in place".
> Ah! I knew I forgot something!! If I remember correctly
> from way way
> back, the GV_USE_DOUBLE_PRECISION_COORD flag was also
> needed for
> general use.
So it's not required for general use. It double the memory foot print
for the coordinate. So it add overhead. YMMV.
Ask a question on any topic and get answers from real people. Go to Yahoo! Answers and share what you know at http://ca.answers.yahoo.com
From: Mario Beauchamp <starged@gm...> - 2009-04-18 01:19:34
On Thu, Apr 16, 2009 at 11:40 AM, s duclos <sylvain_duclos@...> wrote:
> So it's not required for general use. It double the memory foot print
> for the coordinate. So it add overhead. YMMV.
I think it was affecting something else that I cannot remember at this
time... I will investigate and get back to you later.
Get latest updates about Open Source Projects, Conferences and News.