[Scilab-Dev] Scilab MALLOC function.

Jonathan Blanchard BlanchardJ at ieee.org
Sat Sep 27 21:50:46 CEST 2008


Oh ok. So if we use MALLOC it does not consume the Scilab stack space?
I'm asking this because I hacked myself a way to use gmp in Scilab and
I was trying to override the gmp memory management functions to use
the Scilab stack space instead.

Jonathan Blanchard

On Sat, Sep 27, 2008 at 4:17 PM,  <sylvestre.ledru at scilab.org> wrote:
>
>
> On Sat, 27 Sep 2008 11:18:04 -0300, "Jonathan Blanchard"
> <BlanchardJ at ieee.org> wrote:
>> Quick question. Can we assume that the scilab MALLOC function work the
>> same way as the standard malloc. More precisely, is the pointer
>> returned by MALLOC always going to be valid until freed?
> Under Linux, in Scilab, it is calling the standard malloc:
> http://viewvc.scilab.org/bin/cgi/viewvc.cgi/trunk/scilab/libs/MALLOC/src/sci_mem_alloc.c?revision=26187&view=markup
> no more.
>
> Under Windows, we are using heap functions because it is faster. I am
> showing off here ;). I am just repeating what Allan explained me
> (our Windows specialist)
>
> Sylvestre
>
>
>



More information about the dev mailing list