Re: matrix operations and temporary objects?

[Asko Kauppi <askok@...>]

I'd like to make a point that such GC-avoiding optimizations only make sense (imho) when matrices are rather small in size. That is, when the pure mathematical time taken does not grow essential.

Or am I wrong?

We're currently using Lua for matrix calculations with matrix sizes around 50x60 to 500x600. Operations are SSE optimized, but we do not do any operation merging or GC avoidance.

- asko



04.08.2009 05:58, David Manura <dm.lua@math2.org> kirjoitti:

> On Mon, Aug 3, 2009 at 4:46 PM, Javier Guerra<javier@guerrag.com> wrote:
> > two ideas: (not that i have done anything similar)
> >
> > 1: parse a user string with the whole expression to build the operating
> objects:
> > ...
> > 2: override operators in your userdata; but don't make them calculate,
> > make them generate the calculators, a bit like LPEG constructing
> > operators
> 
> Similar types of things have been done in [1-4].
> 
> [1] http://lua-users.org/wiki/ListComprehensions
> [2] http://lua-users.org/wiki/ExpressionTemplatesInLua
> [3] http://lua-users.org/wiki/SourcePreprocessing
> [4] http://met.sourceforge.net/ (C++)
>