From: Joao C. <jc...@fe...> - 2003-03-03 02:05:20
|
On Monday 03 March 2003 00:49, Rafael Laboissiere wrote: > * Rafael Laboissiere <lab...@ps...> [2003-03-03 01:05]: > > For me two, provided that you the data passed back and forth are cast= ed > > with PLFLT. Single precision people should know that they are going = to > > loose something (in this case memory space) if they want to use the g= reat > > plgriddata. However, they should no be prevented to use it because t= he > > API only accepts double. I have already made the changes. I made the cast explicit, so that casual readers will understand that the= =20 types might be different. I think that most compilers will just ignore a cast from a variable that = is=20 already in the final type, like in: =09x =3D (double) y; The cast should represent no overhead if both x and y are doubles. Do you= =20 agree? > Sorry, I have looked carefully into plgridd.c. It seems that plgriddat= a > already uses PLFLT in a consistent way, so my comment above is not > relevant. However, why don't use PLINT instead of int? I never worried about it, except in structure definitions, for padding=20 purposes, and in drivers, where it can matter. Joao |