This is the mail archive of the gsl-discuss@sourceware.org mailing list for the GSL project.
Index Nav: | [Date Index] [Subject Index] [Author Index] [Thread Index] | |
---|---|---|
Message Nav: | [Date Prev] [Date Next] | [Thread Prev] [Thread Next] |
Other format: | [Raw text] |
At Tue, 24 Nov 2009 17:54:46 -0700, Gerard Jungman wrote:Here are header files for a couple different approaches to containers. I didn't bother with any implementations; it seems obvious how to implement most of these functions.
The designs are not complete, but they express most of the important stuff.
Thanks for the document, I have studied the designs this week. It seems that changing to design 1 / 1u / 2 would be trading one set of problems for another. Looking at each case, the change doesn't seem sufficient to justify the compatibility cost.
3) Non-levelised types. These seem to be the price for type safety. In terms of the look/feel, expressions like &row.vector and &column.vector don't seem too unnatural to me.
typedef struct { gsl_marray *m; gsl_const_marray *cm; gsl_marray_1 *m1; gsl_const_marray_1 *cm1; gsl_marray_2 *m2; gsl_const_marray_2 *cm2; gsl_marray_3 *m3; gsl_const_marray_3 *cm3; gsl_vector *vec; gsl_const_vector *cvec; gsl_matrix *mat; gsl_const_matrix *cmat; ... } gsl_container;
-- Tuomo.Keskitalo@iki.fi http://iki.fi/tuomo.keskitalo
Index Nav: | [Date Index] [Subject Index] [Author Index] [Thread Index] | |
---|---|---|
Message Nav: | [Date Prev] [Date Next] | [Thread Prev] [Thread Next] |