johnpitcairn

If I'm using linklist_deleteindex(), I'm guessing from other linklist delete functions that the item will be freed, yes?

Can I rely on memory being correctly freed for any item type, or is it expecting a t_object? I'm storing custom structs previously allocated using getbytes().

linklist_deleteindex-frees-item-but-what-item-type

Never mind ... trying it throws "freeobject: bad object" errors, so I guess I can't.

Might be nice to beef up the comments in linklist.h and others when the Max 5 SDK ships, there's not much there in the way of documentation at present.

Here's some code snips I found in an old project:

buffer = sysmem_newptr(MAX_MSG_SIZE);            // new buffer for next packet,

                            // old buffer will be freed in main thread

linklist_append(xx->s_datalist, buffer);        // copy data out to main 

qelem_set(xx->s_qelem);                    // notify main thread using qelem mechanism

t_cN_packet *packet = linklist_getindex(xx->datalist, 0);

sysmem_freeptr(packet);                    // free the packet

linklist_chuckindex(xx->datalist, 0);            // dump it from the list

buffer = sysmem_newptr(MAX_MSG_SIZE);			// new buffer for next packet,
							// old buffer will be freed in main thread

linklist_append(xx->s_datalist, buffer);		// copy data out to main  
thread
qelem_set(xx->s_qelem);					// notify main thread using qelem mechanism

sysmem_freeptr(packet);					// free the packet
linklist_chuckindex(xx->datalist, 0);			// dump it from the list

linklist_deleteindex frees item, but what item type?