Re: [PD-dev] iem_tab on amd64 WAS: Building extended on amd64

2009-10-13 Thread IOhannes m zmoelnig
Hans-Christoph Steiner wrote: sed -i 's!^\(Depends:.*\)!\1 , libfftw3-3, zlib1g (= 1:1.2.3.3.dfsg-1), libogg0 (= 1.0rc3), liblame0 (= 3.97), libvorbis0a (= 1.2.0), libgsl0ldbl (= 1.9), libimlib2, libdv4, tk8.5 (= 8.5.0), libquicktime1 (= 2:1.0.0+debian), libgl1-mesa | libgl1, libsdl1.2debian

[PD-dev] Memory reallocation problem

2009-10-13 Thread Isidro Gonzalez
Hi: I am triying to allocate a n*n matrix of a type defined structure of data. The pd external object example I'm sending attached is very simple: each time it receives any message except the clear message it increments a counter and reallocate a matrix of n*n members where n is the number

Re: [PD-dev] Memory reallocation problem

2009-10-13 Thread Justin Glenn Smith
Isidro Gonzalez wrote: Hi: I am triying to allocate a n*n matrix of a type defined structure of data. The pd external object example I'm sending attached is very simple: each time it receives any message except the clear message it increments a counter and reallocate a matrix of n*n members

Re: [PD-dev] Memory reallocation problem

2009-10-13 Thread Isidro Gonzalez
Many thanks for your kind answer. I´m surprised because the way I use to allocate memory is the most commonly used. Wouldn´t initializing the pointers to NULL destroy all the contents of previous memory they hold, if any...? So, why to use realloc this way, then? I would use free and malloc,

Re: [PD-dev] Memory reallocation problem

2009-10-13 Thread Justin Glenn Smith
Isidro Gonzalez wrote: Many thanks for your kind answer. I´m surprised because the way I use to allocate memory is the most commonly used. Wouldn´t initializing the pointers to NULL destroy all the contents of previous memory they hold, if any...? So, why to use realloc this way, then? I