Hello Sam, I have lost track of the status of the ipack_device_register() error handing and free() issues. However, looking at the issue I am not sure it is required to split the function. IMHO what we need are clearly defined rules when the IPack stack becomes responsible for handling the freeing of memory (e.g. when control over the device is passed). I propose control is passed when ipack_device_register() is called--independent of its success.
Please find an implementation of this scheme as replies to this email. Best Regards, Jens ------------------------------------------------------------------------------ Precog is a next-generation analytics platform capable of advanced analytics on semi-structured data. The platform includes APIs for building apps and a phenomenal toolset for data science. Developers can use our toolset for easy data analysis & visualization. Get a free account! http://www2.precog.com/precogplatform/slashdotnewsletter _______________________________________________ Industrypack-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/industrypack-devel
