Hi, Alan, On Jan 6, 2010, at 9:03 , Alan W. Irwin wrote:
> If we have a mixture of C and Fortran ordering for the two-dimensional > arrays in our API, we should decide which convention we should use > in our > API and convert to it if/when we decide to do other major API > breakage we > have been discussing. I guess I joined the list after that discussion, but I think it would be great if the API supported the following four ways of passing in 2D data... 1) 1D array of nx pointers to 1D arrays of ny values 2) 1D array of ny pointers to 1D arrays of nx values 3) Pointer to 1D array of nx*ny values in row major order 4) Pointer to 1D array of nx*ny values in column major order This may be somewhat of a grandiose, idealistic wish, but it would support the most common ways of specifying 2D data without requiring (potentially expensive) transposition of the data. I haven't gotten too far into the other 3D-ish functions yet, but some (e.g. plcont) accept a "transformation" function pointer through which lookups occur. Perhaps this mechanism (or something similar) could be used to provide the level of flexibility I'm suggesting (and beyond!). Just an idea, Dave ------------------------------------------------------------------------------ This SF.Net email is sponsored by the Verizon Developer Community Take advantage of Verizon's best-in-class app development support A streamlined, 14 day to market process makes app distribution fast and easy Join now and get one step closer to millions of Verizon customers http://p.sf.net/sfu/verizon-dev2dev _______________________________________________ Plplot-devel mailing list Plplot-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/plplot-devel
