On Thursday 18 July 2013 at 18:45, Steven Yi wrote:
Hi Ed,I think the ARRAYDAT should already be created by the compiler by thetime you see it in your opcode. However, it's dimensions and data maynot be initialized, which you may need to then modify yourself. I'mnot sure about needing a deinit callback. I don't know what thestandard practice is for freeing up memory for variables; perhaps weneed to add a var_free function to CS_TYPE to automatically handlethat...Otherwise, I'd look at Opcodes/arrays.c and use the functions Johnwrote as a model.Good luck!stevenOn Wed, Jul 17, 2013 at 10:06 AM, Edward Costello<edwardcostello@gmail.com> wrote:Hi,When creating a custom array opcode, for instance one that takes 2 arrays asinput and give 1 array as output, in the initialisation function for theopcode, when creating the output array does one create an ARRAYINIT structand pass that to the array_init function? Conversely is there a need to callthe array_del function from a RegisterDeinitCallback?Thanks--Edward Costello------------------------------------------------------------------------------See everything from the browser to the database with AppDynamicsGet end-to-end visibility with application monitoring from AppDynamicsIsolate bottlenecks and diagnose root cause in seconds.Start your free trial of AppDynamics Pro today!_______________________________________________Csound-devel mailing list------------------------------------------------------------------------------See everything from the browser to the database with AppDynamicsGet end-to-end visibility with application monitoring from AppDynamicsIsolate bottlenecks and diagnose root cause in seconds.Start your free trial of AppDynamics Pro today!_______________________________________________Csound-devel mailing list