From: H. H. <hen...@gm...> - 2008-08-24 20:03:46
|
Good. I will be making the changes in the upcoming commits, and updating the test cases for them. I have also added some explaining comments for the matrix layouts in my last commit: typedef struct { union { /* Matrix layout: | data[0] data[2] | | data[1] data[3] | */ GLfloat data[4]; struct { /* Matrix layout: | m00 m01 | | m10 m11 | */ GLfloat m00, m10, m01, m11; }; }; } GLMmat2f; All this will of course need to go to the GLM API documentation also, in time. On Sun, Aug 24, 2008 at 10:50 PM, Jason McKesson <ko...@gm...> wrote: > Henri Häkkinen wrote: > > Another open issues has came up: > > > > Do you think we should allow something like this: > > > > glmMatInverse2f (&mat, &mat); > > glmMatTranspose2f (&mat, &mat); > > glmVecAdd2f (&vec, &vec, &vec); > > > > For some functions, this add some additional processing since it needs > > to store temporary values of matrix members before performing an > > operation, such as: > > > > ... > > > > My proposal is that we allow glmMatInverse2f (&mat, &mat) and live > > with the additional overhead. -Self funcs may still be included for > > convenience (at some later GLM versions). > Agreed. It adheres to the principle of least surprise. The less-careful > user will expect to be able to pass the same parameter, or outputs as > inputs, and we should allow it. > > ------------------------------------------------------------------------- > This SF.Net email is sponsored by the Moblin Your Move Developer's > challenge > Build the coolest Linux based applications with Moblin SDK & win great > prizes > Grand prize is a trip for two to an Open Source event anywhere in the world > http://moblin-contest.org/redirect.php?banner_id=100&url=/ > _______________________________________________ > Glsdk-devel mailing list > Gls...@li... > https://lists.sourceforge.net/lists/listinfo/glsdk-devel > -- Henri 'henux' Häkkinen |