[PD-dev] porting MSP externals - sysmem_newptrclear and sysmem_freeptr

[Ed Kelly]

Hi Devs,
I'm attempting to port a library of MSP externals for LPC analysis and resynthesis.I've come across these elements from the Max API:
t_ptr sysmem_newptrclear (long size)andvoid sysmem_freeptr (void *ptr)
My head has hit a block, and I need to learn about how Pd deals with these aspects of memory / pointer allocation.Do I need to just init a pointer in the code?
enclosed is the original of one of the externals (mbc.blit~.c) and my first attempt at porting it (lpc_blit~.c)
Enlightnment awaits...I hope.Ed _-_-_-_-_-_-_-^-_-_-_-_-_-_-_

For Lone Shark releases, Pure Data software and published Research, go to http://sharktracks.co.uk 
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.puredata.info/pipermail/pd-dev/attachments/20180128/f0de171a/attachment-0001.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: lpc_blit~.c
Type: text/x-csrc
Size: 9850 bytes
Desc: not available
URL: <http://lists.puredata.info/pipermail/pd-dev/attachments/20180128/f0de171a/attachment-0002.c>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: mbc.blit~.c
Type: text/x-csrc
Size: 10711 bytes
Desc: not available
URL: <http://lists.puredata.info/pipermail/pd-dev/attachments/20180128/f0de171a/attachment-0003.c>