Talk:Element-wise operations: Difference between revisions

From Rosetta Code
Content added Content deleted
(Created page with "Can we cut back on the matrix fetish? If you need it for serious work, go get a good quality matrix library for your language. Implementing your own matrix class is always a bad...")
 
(Additional disclaimer?)
Line 2: Line 2:


And the task with the Lisp example is lousy. Do you check if the dimensions match? Can you even tell if the object is indeed a matrix? If the dimensions are wrong, does it just blow up or silently give some undefined answer? -- [[User:Ledrug|Ledrug]] 18:57, 9 June 2011 (UTC)
And the task with the Lisp example is lousy. Do you check if the dimensions match? Can you even tell if the object is indeed a matrix? If the dimensions are wrong, does it just blow up or silently give some undefined answer? -- [[User:Ledrug|Ledrug]] 18:57, 9 June 2011 (UTC)
:It may be fine for educational purposes as long as we add a disclaimer saying that this is probably not the best way to do things in most languages (although we already have a disclaimer [[Rosetta_Code:General_disclaimer|here]] that says code here shouldn't be used for so called "serious work"). This task is probably pretty much perfect for array programming languages like [[APL]] and [[J]]. --[[User:Mwn3d|Mwn3d]] 20:54, 9 June 2011 (UTC)

Revision as of 20:54, 9 June 2011

Can we cut back on the matrix fetish? If you need it for serious work, go get a good quality matrix library for your language. Implementing your own matrix class is always a bad idea. The task could have said "vector", which is a lot simpler to write a short clean implementation for and much more to the point.

And the task with the Lisp example is lousy. Do you check if the dimensions match? Can you even tell if the object is indeed a matrix? If the dimensions are wrong, does it just blow up or silently give some undefined answer? -- Ledrug 18:57, 9 June 2011 (UTC)

It may be fine for educational purposes as long as we add a disclaimer saying that this is probably not the best way to do things in most languages (although we already have a disclaimer here that says code here shouldn't be used for so called "serious work"). This task is probably pretty much perfect for array programming languages like APL and J. --Mwn3d 20:54, 9 June 2011 (UTC)