« Return to Thread: .oct files - keeping state across calls

Re: .oct files - keeping state across calls

by dbateman2 :: Rate this Message:

Reply to Author | View in Thread

Christophe Tournery wrote:

> Thanks for the tip, I did not know mlock().
>
> However the problem is still there. The list of handles has a
> different memory address when calling the mylib_init() function and
> when calling the mylib_process() function. Has there been major
> changes from 3.0 to 3.2 regarding loading oct files?
>
> Do you guys encounter this design problem often or is there a very
> simple solution I do not see?
>
At this point I'm not sure there is a problem at all. Could you send a
complete simple example demonstrating the problem..

D.


--
David Bateman                                dbateman@...
35 rue Gambetta                              +33 1 46 04 02 18 (Home)
92100 Boulogne-Billancourt FRANCE            +33 6 72 01 06 33 (Mob)

_______________________________________________
Help-octave mailing list
Help-octave@...
https://www-old.cae.wisc.edu/mailman/listinfo/help-octave

 « Return to Thread: .oct files - keeping state across calls