From: Rafael L. <lab...@ps...> - 2003-03-03 00:18:34
|
* Joao Cardoso <jc...@fe...> [2003-03-02 23:27]: > I understand that situation. How could it be solved? > > 1-Adding another configure option --short-in-memory or perhaps > --with-huge-data? In that case, if --with-double=no --with-huge-data=yes were > specified, then nn/csa would not be built; if only --with-double=no, than > floats would be converted to doubles and vice versa. > > 2-Even if --with-double=no, we always convert floats<->doubles, but rely that > users know what they are doing and would not call the nn/csa based gridding > algorithms? If they would they would do it just once -- learn by error. > > 3-Or making --with-qhull=no by default? I vote against this last one :() > > The second option seems reasonable to me. For me two, provided that you the data passed back and forth are casted 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 great plgriddata. However, they should no be prevented to use it because the API only accepts double. > It could be run by configure, then users would just sent the result to us. > Stupid woman!(1) don't you see that we already have this? It's called > config.summary! I know, I was thinking about something more complete, including the architecture and other things. And yes, config.summary is a good starting point. -- Rafael |