Re: [PD] pd, openCV, pointers and indirection.

2009-10-05 Thread Loic Kessous
thanks Mathieu, it is still not clear for me what make things faster in one case or another but it helps. loic PS: what do you call Martin's strings ? On 3 oct. 09, at 23:22, Mathieu Bouchard wrote: On Sat, 3 Oct 2009, Loic Kessous wrote: I understand your point of view, but I am more

Re: [PD] pd, openCV, pointers and indirection.

2009-10-05 Thread Mathieu Bouchard
On Mon, 5 Oct 2009, Loic Kessous wrote: thanks Mathieu, it is still not clear for me what make things faster in one case or another but it helps. 1. data spacing: the more your data is spaced in memory, the more the cache has to load lots of data, because it assumes that the data is not

Re: [PD] pd, openCV, pointers and indirection.

2009-10-05 Thread Mathieu Bouchard
On Mon, 5 Oct 2009, Mathieu Bouchard wrote: On Mon, 5 Oct 2009, Loic Kessous wrote: loic PS: what do you call Martin's strings ? I thought I knew, but I borked that. Martin's strings are [mrpeach/str], but they don't use pd lists of floats, they use a custom atom type called BLOB, And the

[PD] pd, openCV, pointers and indirection.

2009-10-03 Thread Mathieu Bouchard
On Sat, 3 Oct 2009, Loic Kessous wrote: I understand your point of view, but I am more interested buy the approach than the implementation itself. I mean passing a pointer and not the image itself. Passing the image itself is largely a myth anyway. At a first level, Pd doesn't always pass